In this post, I explain why at Slingboards Lab (my new venture), we have decided to build an hybrid mobile app instead of a native or HTML5 app.
I said in the past and I will say it again: the tablet is a completely different platform than the PC and in this sense it has its own natural structure for UX experiences.
Each space has a natural structure, which is an organizing principle that helps people form a mental model of how they think about and navigate that space. Rooms are the structure of homes, neighborhoods and streets are fixed structure of cities, aisles are the structure for most stores, and Web pages are the structure for Web sites.
The natural structure for the PC experience was the desktop and accompanying folder/ file system. Influenced by notions of containment and place, this structure allowed people to traverse their personal file systems with ease. Within the PC platform, applications are often relegated to the role of a secondary actor. Files are the stars of the desktop experience, whereas applications are merely the tools that make files.
In contrast, within the tablet platform, applications are the star, making them a natural structure for mobile experiences. In fact, we can summarize the tablet experience as a list of “native” apps. Disappointing by its simplicity, this minimalist approach has proven effective. Tablet application marketplaces also reinforce the app as the natural structure for mobile experiences. A tablet platform’s value and popularity are largely attributed to the depth and breadth of its App Store portfolio.
Nowadays, the main challenge for organizations is to develop mobile applications. However, we no longer control the mobile platform in use. Tablets are provided by individuals according to their personal preferences. Some will bring Apple IOS devices such as the iPad while other will arrive with Microsoft windows 8 tablets or with Google Androids tablets such as the Amazon Fire. This diversification of mobile devices would not be a handicap if there was a single programming model to build native apps. Unfortunately, this is not the case. Native apps are specific to a given mobile platform and are built using the development tools and language that the respective platform supports (e.g., Xcode and Objective-C with Apple iOS, Eclipse and Java with Google Android).
So, if you are a young startup like Slingboards-Lab, should you go native, HTML5 or hybrid? Faced with this fundamental issue, I must acquiesce with Stephen Forte: A startup should never, ever, go native. The very nature of a startup is that you have little money and need to be super fast on the market to validate your assumptions (and discover that you’re wrong). On the other hand, because the apps are the natural structure for mobile experience, I think opting for an HTML5 app is a mistake. So there is only one logical choice; the hybrid app.
This thinking explains why we have chosen to build Slingboards as an hybrid app. We are working hard and soon we will be able to share with you the results of our discovery. Stay tune.