sweater:web_implementation
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
sweater:web_implementation [2019/03/05 02:16] – mithat | sweater:web_implementation [2019/03/05 03:24] (current) – [What's in front?] mithat | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Sweater Web Implementation ====== | ====== Sweater Web Implementation ====== | ||
- | Even though we may have decided to build the app using Web technologies, | + | ===== What's in front? ===== |
+ | |||
+ | 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 | ||
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:// | ||
- | We still need to consider what kinds of frameworks or libraries we might leverage for the UX/UI experience (e.g., Bootstrap, Materialize) and the overall app structure (e.g., Vue.js. React, Angular). Whether we use a UI/UX framework will depend a lot on what the [[design]] for the app specifies. This in turn could influence the selection of core technology used for the app structure. | + | ===== How plain is plain? ===== |
+ | |||
+ | We still need to consider what kinds of front-end | ||
- | Let's start by looking at what happens with just a [[Plain-old Web tech implementation]]. | + | But for the hell of it, let's start by looking at what happens with just a [[Plain-old Web tech implementation]]. |
sweater/web_implementation.1551752185.txt.gz · Last modified: 2019/03/05 02:16 by mithat