Mobile Web Apps with Native App UX – Take Care with NavigationDecember 8th, 2010 by Trilibis Blogging Team
With mobile web apps, the UI presents a browser frame overlay, generating a different set of expectations from a user compared to a native app. This is true even if the web app closely resembles a native app. The main difference is that the user intuitively expects to be able to use the browser’s embedded navigational controls rather than only the integrated navigational elements of the mobile web app. This is particularly true for the ‘back’ operation. I’ve seen a number of mobile web applications where a‘back’ operation took the user outside of the web app to the previously visited site, even though the user was multiple clicks into the web app. In essence, such design provides a forced abandonment sequence, which is certainly not desirable for any brand. And it is an unexpected and annoying result for the user.
As such, any mobile web application must accommodate browser navigation controls to provide a good user experience. If the mobile web application uses a native code wrapper to hide the browser’s frame, then obviously this no longer applies. However, a native wrapper is often not the entry point to a mobile web application. So unless the sole distribution is the app store with the native wrapper, this will be a problem for your mobile web app (though beware – many Android handsets permanently embed the ‘Back’ operation into the handset, so you will still need to accommodate for that).