GlueCon 2013 Notes: Single Page Architectures: The API and Appification for the Web Steven Willmott, 3Scale

Single Page Architectures: The API and Appification for the Web Steven Willmott, 3Scale (@njyx and @3scale)

• Plenty of toolkits available to build SPAs
• Upsides – more responsive, push support, nice interfaces with similarity to mobile/desktop dev
• Downsides – harder to find JS skills, need modern browsers, less tooling
• Evernote is a great example – they support a variety of platforms, browsers to be a note-taking platform
• Zendesk is now single page – use ember, provide an example App for developers to get started using their API
• SaaS apps are more likely to adopt, ecommerce/content less likely
• Deep linking, SEO/discoverability, and RSS/Findability are the likely causes of holding out on SPA
• SPAs may enable separation of free and paid content
• APIs form the basis for interactions with oAuth helping
• Devices, such as printers, Live Scribe Pen, etc can consume capture/publish from/to APIs
• SPAs help drive architectures to APIs for consumption by a variety of sources (intended and unintended)
• Take aways: SPA adoption will increase, will be potentially disruptive to the web itself, lots of work to do

Update: the slide deck is now available