sweater:web_implementation
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
sweater:web_implementation [2019/03/05 03:08] – [How plain is plain?] mithat | sweater:web_implementation [2019/03/05 03:24] (current) – [What's in front?] mithat | ||
---|---|---|---|
Line 5: | Line 5: | ||
Even though we may have decided to build the app using Web technologies, | Even though we may have decided to build the app using Web technologies, | ||
- | In the case of Sweater, we could design the app to be almost completely backend driven. But it's hard to make a good case for this. Having the backend get weather data for the current user (making sure you keep track of the current user), compose a page, send that back to the client, and then design a mechanism that periodically refreshes the page makes little sense when the client can do it all in the front-end and do it with grace. | + | In the case of Sweater, we could design the app to be almost completely backend driven. But it's hard to make a good case for this. Having the backend get weather data for the current user (making sure you keep track of the current user's location), compose a page, send that back to the client, and then design a mechanism that periodically refreshes the page makes little sense when the client can do it all in the front-end and do it with grace. |
So, it looks like Sweater will be a relatively simple full-on [[https:// | So, it looks like Sweater will be a relatively simple full-on [[https:// |
sweater/web_implementation.txt · Last modified: 2019/03/05 03:24 by mithat