sweater:implementation
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
sweater:implementation [2019/03/05 02:14] – [Choosing technologies] mithat | sweater:implementation [2019/03/05 02:46] – [Sweater Implementation] mithat | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Sweater Implementation ====== | ====== Sweater Implementation ====== | ||
- | A crucial question we need to decide is what technology the Sweater app should | + | A crucial question we need to decide is what technology the Sweater app will be built with. In general, this decision depends |
- | The potentially evolving design requirements for the project are discussed [[design|elsewhere]]. Some of the business needs one might need to consider | + | The potentially evolving design requirements for this project are discussed [[design|elsewhere]]. |
+ | |||
+ | Some of the business needs one might need to consider | ||
* How soon must the app ship? | * How soon must the app ship? | ||
* How important is it that features can be added? | * How important is it that features can be added? | ||
- | * How important is it that the styling can be changed? | + | * How important is it that the UI/styling can be changed? |
+ | For Sweater, I am going to say that the app needs to ship only as soon as it's ready, but preferable not before another major JavaScript release. I'm also going to say that the app will always be simple, that's its main draw, so adding a lot of new features will be unlikely. Finally, it would be cool if Sweater could wear different sweaters, so it would be good to design the apps structure to make applying different UI/styling not unreasonable. But this isn't a must-have. | ||
===== Choosing technologies ===== | ===== Choosing technologies ===== | ||
sweater/implementation.txt · Last modified: 2019/03/05 03:06 by mithat