Even though we may have decided to build the app using Web technologies, our decisions about technologies isn't done. Something that would be helpful to have an understanding of early on is how much to rely on backend processes and how much to do in the front end. In the case of Sweater, we could design the app to be almost completely backend driven. But it's hard to make a good business case for this. Having the backend go out and get weather data for the specific user (making sure you keep track of the current user), compose a page and send that back to the client, and then forcing the update of that 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 SPA.

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.

Let's start by looking at what happens with just a Plain-old Web tech implementation.