Today’s browsers sport amazing capabilities, truly graduating from markup renderers to sophisticated app run-times. We're sure to see some amazing new web applications just over the horizon that take advantage of these new capabilities.
At the same time, the mobile ecosystem is white hot and we’re seeing a range of start-ups pursue an "app-only" strategy. What relationship do mobile “apps” have with the web and how will these two communities co-exist into the future? Also, how do developers target all of these different platforms? Which should they embrace and which should they ignore?
Join Ben and Dion as they explore these issues.
The thick client is back! Pushing entire applications down to the client has become a lot more popular in recent times, and is especially interesting for mobile devices.
However, building solid and polished single-page applications means that we need to replicate a lot of native browser behaviour. When we don’t, we’ll annoy or even scare away our users.
This talk will cover both the pitfalls and opportunities of single-page applications, focusing on the native behaviour that your app needs to provide in order to behave like an actual web site, while fixing a lot of the usability issues that web sites usually have.
For example, this covers dealing with proper URLs, without breaking back and forward buttons, using the still somewhat new HTML5 history API.
We’ll look at both the existing frameworks that help implement this, and those still lacking.
10th February 2012