Skip to main content

Has The Era Of Mobile Web Apps Finally Come?

It has long been a subject of an argument, essentially since the advent of the mobile web itself more than ten years ago: the anticipation of mobile web taking over the native mobile apps - repeating the success of desktop web on mobile devices - has been just that - the anticipation.

The beauty of "write once, run everywhere" was once again challenged by the realities of computing power and user experience compromises, as it was back in 90s when Java was created with the same promise only to fail delivering on it.

No matter which year is printed on the calendar, the verdict has always been the same: "mobile web apps are promising, but not quite there yet, but wait, they are just around the corner".

At the same time, the times of one-man-show stunts making big $$ by developing mobile apps are over. The industry has increasingly professionalized and the need to support three major mobile platforms (iOS, Android, Windows) is heavily taxing native app development and raising the bar for entry.

Recent apps on my phone - guess which are native vs. web apps.

However, I have seen two interesting developments in the past year, which should make you reconsider the mobile app strategy:
  1. Since Android 5.0, mobile Chrome browser supports the "Marge tabs and apps" feature, which makes web applications such as Facebook or Twitter look like native apps when presented in the recent apps carousel on Android.
  2. With the support of push notifications in Chrome and other mobile browsers, the ability of mobile web apps to catch user's attention and bring her back to the app, many times the primary reason for developing the native app, has become almost obsolete as well.
"Merge tabs and apps" feature in Chrome
It is indisputable, that the user experience of native apps still beats mobile web apps, so for apps I use every day, I prefer native apps. However, for less frequented apps, the situation changes dramatically in my eyes: I hesitate to install apps on my phone just to try them out or use them once or occasionally. My primary concern is privacy & security, but besides that it is also a matter of convenience - the bloat some apps cause, the precious space consumed by them and ironically even the frequent app updates: a rarely used native app may consume more battery by frequent updates from the app store than actually running on the phone. It has been long time ago I uninstall Facebook from my phone and I am completely happy to use the mobile web version for the occasional visits.


Web push notifications settings.
Given my experience above, I believe the mobile web apps should seriously be considered for use cases where you are not aiming at daily usage. Good examples would be various reservation systems, ticketing apps for buying cultural events tickets, travel booking apps, loyalty programs and others. In these cases, a mobile web app removes the friction - no need to install a native app - while still providing decent user experience. Last but last not least - the development and maintenance cost are likely to be much lower than for native apps for multiple platforms and a lot of the infrastructure can be shared between the mobile web app and the desktop web version of the service.

So think twice before you launch that job postings for Android, iOS and Windows mobile developers for your next project - it may well be the case the mobile web can expedite your journey to the customers and save you $$, if your application is intended for occasional transactional use.

Labels:

Comments

Post a Comment

Popular posts from this blog

Coasting Like a PRO

Roughly three months into driving 225xe, it seems about right time come back to revisit the initial impressions and see how the car fares in long-term usage. In this post, I want to focus on the 225xe driving modes of which the car offers aplenty. First, there are the three traditional BMW Driving Experience modes: COMFORT, SPORT, and ECO PRO, which come fitted on non-hybrid powertrains as well. Then there are the eDrive modes: AUTO eDrive, MAX eDrive, and SAVE BATTERY. To complicate this even further, moving the gear stick to the left at any time switches the automatic gearbox to the sports mode, so there are two gearbox modes: Drive and Sport/Manual which allows sequential gear shifts. So in theory, there are 3 x 3 x 2 = 18 combinations, in practice, some of the combinations are mutually exclusive, so it is not so extreme as it seems. What is apparent though is that BMW keeps adding new options while maintaining the legacy options as well without thinking about consolidation. This
Post a Comment
Read more

First Month of Active Touring

Putting my money where my mouth is, I took on the adventure of buying a plug-in hybrid. A few years back, I used to drive a car only for weekend getaways, so an SUV seemed to be a logical choice. At only fifteen thousand kilometers driven annually, the fuel economy was not a significant issue, the driving experience was the main thing. During the past few years with family and small kids, the car usage became more spread out throughout the week. With that said, I noticed we maintain two very distinct driving patterns: many short trips around Prague during the week to get kids to school and sports and then longer trips, roughly 100 miles each direction, during the weekends. With short distances and many cold starts due to the city driving on the workdays, the already poor fuel economy of an SUV deteriorated further. I realized when our car was up for renewal that it was almost as if we needed two different vehicles for two different use cases - an electric vehicle for city driving a
Post a Comment
Read more

Version 2.0 Syndrome - Why the Software Architecture Matters

"Guys you will never have a chance to build the version 2.0, you have to get it right from the get-go, or keep suffering from your mistakes for the lifetime of the product." - Jiri Karpeta, my boss at LCS International, used to say. It was back in 1995, and while LCS's bread and butter were Helios, an ERP for the SMB segment, we were busy building Noris - the future LCS's flagship ERP for larger enterprises. Of course, given the above philosophy, LCS was quite heavily invested in CASE tools to support our software design efforts. That's where I learned the first time that software modeling matters. But back to the original statement above that you "never get a chance to build the version 2.0" . It may sound too harsh, too fatalistic. Well, you may be right, there are always exceptions to the rule. While I don't have exact statistics at hand, my experience shows that the statement is more often correct than not. I have interviewed hundreds of softw
Post a Comment
Read more