Loose notes from SXSW 2011 session: One Codebase, Endless Possibilities: Real HTML5 Hacking
HTML5 is no question the “buzzword du jour” in tech nowadays, but looking past the vernacular cruft one will discover that the HTML5 technology STACK is actually an incredibly powerful & useful framework for apps well beyond the traditional web browser. Massive companies like Google and Hewlett Packard are placing huge bets on the future of “HTML5 App development”. From HP/Palm’s WebOS to be used in their mobility products to Google’s Chrome OS, HTML5 is not simply another buzzword that can be treated as a mere passing trend, but should actually be taken seriously for app development. But what makes up the HTML5 stack and how will it truly be the future of software? What are the benefits & risks associated with using the HTML5 stack? Prove to me it works. All of these questions & demands will be answered & showcased in the presentation including important issues such as: What constitutes the HTML5 stack Benefits of using the HTML5 stack Use a single codebase Rapidly prototype an app targetting multiple devices including: iPhone, iPad, Android Devices, Chrome OS Devices, Mobile Webkit Browsers, Desktop Browsers Target thousands of developers for extensibility & community development .
If your mobile app is written in both Java (Android) and Objective C (iOS) and Rails (web app), then you have three code bases to update just to change your company logo. Add QA into the mix and things get really messy. The business guys hate this – gets expensive fast.
Using the Web Stack significantly reduces development costs, design costs, simplifies maintenance, and you can do it all with a single codebase.
*** Tools for the Web Stack ***
– Sencha Touch – HTML5-ish development toolkit for creating near-native applications using web technologies.
– Appcelerator Titanium – All of the above but also creates native desktop applications.
– JQuery Mobile – Gracefully degrades to crappy devices.
Demo app example open sourced at https://github.com/joemccann/freebeernearme
Responsive design: Hide UI elements as browser resizes – don’t just squish them or show horizontal sliders, but literally hide them when browser goes small.
Geolocation across these devices is not as accurate as you may think.