Closed maryi closed 8 years ago
I agree with your idea for planned permanence. It makes sense to me that people working on short term projects are more likely to use free tools than paid ones.
I think this could be a good question to ask in general, but we might run into problems with some applications like github and slack which are both web based free and desktop apps. also I think both slack and github work well for long term and short term projects. maybe this could be one part of the classification for planned permanence but I think we might need a second question to resolve some cases.
Excellent point @eli4 ... we have some hybrid apps!.. We can make the selection non-exclusive.. So for example, we could ask what are the "possible modes" for the application? .. making the question non-exclusive we could include cases like Slack. What do you think?
@maryi sounds good
I am thinking make this selection non-exclusive. Perhaps for low planned permanence apps which are free and easily accessible are ordered first.
We should get some mock ups of the app display page wireframed so we can start imaging what that page looks like after users enter their MoCA description.
Planned Permanence dimension
I think we shouldn't have this dimension in the specific case when the user is registering a new app into the system .... We can decide about this based on different information.
For instance: We can ask the user if the the app is web based, if it is free, if it requires to download an installer, if you need to register in order to use it.. and then on the back of our system we can create a hierarchy. Say:
For Planned permanence LOW to HIGH Web based - free Web based - free - with registration Desktop app - free Desktop app - free - with registration Web based - payed - with registration Desktop app - payed - with registration
What do you think?