M
miaosidea
The main point:
Does it possible if we build in a basic functionality in the operation
system (view it as ppd lic), something like powershell, that means, end users
who got a genuine lic would get a long-time trial (e.g. 1 yr, it's free in
the trial, and it is open for them to give suggestions or feedbacks in the
trial). 1 year later, consumers could have two choices:
1. they are very satisfied with trial and wanna buy genuine software
2. they wanna continue to use the software but in a full-subscription mode
3. they wanna use the software in a specific way - continue to use
often-used functionalities but stop less-used parts, called it
partial-subscription. In a word, the usage of software is going to be more
flexible, even consumers could decide what they want and what they do not
want. Why not provide a path to the case? Sounds concepts of software
customize appears, right?
advantage:
a. Flexible
b. put the decision to the end users
c. Expandable. Take ppd lic(s) as core, then according to the suggestions or
feedbacks we have got, the increasing stronger work will present
d. Once app does itself does not work, end user could get a basic
functionality not block themselves
e. Easy to regression.
disadvantage:
a. Favorite. In this case, it is important to define ppd lic, even requires
clearly know what kind of functionality they often run into (involving new
ones)
b. Security. For partial-subscription users, how much we would protect them?
Risk could generates on the boundary of partial-subscription and
non-subscription part. How many efforts we could do to launch a new
functionality which previously not be used such as paths, ux or concept of
service-trigger provide to end uses, once service has been triggered, it
indicates end user eager to continue using in partial mode, however, we could
probably give paths or ux to confirm to ensure the formal subscription.
c. Advanced Security. License consumption failed or hit the temper. This
could probably occurs in the case of conbination of partial-subscription -
subscription new functionalities for a period - cancel subscription before
expired, the problem would probably appears on the boundary.
4. Uninstall and reinstall.
For these kind of consumers, on one hand, continue to either direct them use
genuine software or still study their feedbacks is a good choice. Another
choice is going to take part in trail software experience plan to see the
contributions. Here, I use the word "study", that means we could measures in
accordance with their favorites, pursues to use, bla bla bla ...
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...d1f215&dg=microsoft.public.word.docmanagement
Does it possible if we build in a basic functionality in the operation
system (view it as ppd lic), something like powershell, that means, end users
who got a genuine lic would get a long-time trial (e.g. 1 yr, it's free in
the trial, and it is open for them to give suggestions or feedbacks in the
trial). 1 year later, consumers could have two choices:
1. they are very satisfied with trial and wanna buy genuine software
2. they wanna continue to use the software but in a full-subscription mode
3. they wanna use the software in a specific way - continue to use
often-used functionalities but stop less-used parts, called it
partial-subscription. In a word, the usage of software is going to be more
flexible, even consumers could decide what they want and what they do not
want. Why not provide a path to the case? Sounds concepts of software
customize appears, right?
advantage:
a. Flexible
b. put the decision to the end users
c. Expandable. Take ppd lic(s) as core, then according to the suggestions or
feedbacks we have got, the increasing stronger work will present
d. Once app does itself does not work, end user could get a basic
functionality not block themselves
e. Easy to regression.
disadvantage:
a. Favorite. In this case, it is important to define ppd lic, even requires
clearly know what kind of functionality they often run into (involving new
ones)
b. Security. For partial-subscription users, how much we would protect them?
Risk could generates on the boundary of partial-subscription and
non-subscription part. How many efforts we could do to launch a new
functionality which previously not be used such as paths, ux or concept of
service-trigger provide to end uses, once service has been triggered, it
indicates end user eager to continue using in partial mode, however, we could
probably give paths or ux to confirm to ensure the formal subscription.
c. Advanced Security. License consumption failed or hit the temper. This
could probably occurs in the case of conbination of partial-subscription -
subscription new functionalities for a period - cancel subscription before
expired, the problem would probably appears on the boundary.
4. Uninstall and reinstall.
For these kind of consumers, on one hand, continue to either direct them use
genuine software or still study their feedbacks is a good choice. Another
choice is going to take part in trail software experience plan to see the
contributions. Here, I use the word "study", that means we could measures in
accordance with their favorites, pursues to use, bla bla bla ...
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...d1f215&dg=microsoft.public.word.docmanagement