Single Page Application

Reading time ~1 minute

If I’m using Angular which is a framework to build Single Page Applications (SPA), maybe I should understand what an SPA is.

Of course there is the Wikipedia article, but I like this discussion of SPA’s. It addresses my misconception that an SPA could house a simple CRUD workflow but it would take multiple “pages” to create a full fledged application. In actuallity a “single page” is the entry into the application. Then through the combination of HTML, HTTP, and JSON that single page is transformed is into the various views of the application. You don’t link to other pages to get different functionality.

You also don’t lose browser navigation which surprised me. I thought doing DOM manipulation on this level would break the web paradigm, but it doesn’t so I’m going to need to learn how Angular does this.

On a funny note, the author likes the term Rich Web Application which makes me think he didn’t live through the horror of Rich Internet Applications. Nobody in their right mind would want any connection with Flash, Silverlight, or any of the other abominations that polluted the web.

How Do I Document?

I don't have an answer to the question. I'm just riffing here. Trying to figure out how to create value for a yet to be determined audien...… Continue reading

Alexa Skill - Part 4

Published on September 19, 2018

Alexa Skill - Part 3

Published on September 16, 2018