The Future Of The Mobile Web Just Became Bright

Great apps are generally native apps. I discuss with our clients daily that, given unlimited time and money, every app should be native, as this affords the ultimate in user experience. Unfortunately, budgets rarely use the word "unlimited," so compromises must be made. Commonly, one of the first tactical directions away from native is to the mobile web. This asks users to painfully type a URL on their device and then suffer through a browser experience that takes away from the immersive experience that the app should convey. This all changed with Mozilla Junior, a browser being developed for the iPad targeted directly at the iPad user. Thanks to some outstanding design decisions, the mobile web now has a very bright future:

  • A browser without chrome. This is the biggest stylistic deterrent to mobile apps. Today’s mobile web experience is always wrapped in browser “stuff” known as chrome (URL bar, navigation buttons, toolbars, etc.). Junior changes this by providing a browser with no chrome at all. This allows you, the mobile web developer, to use the entire screen as your app canvas. Native interactions (swipes/long presses/etc.) can now be fully implemented without fear of accidentally pressing a browser button.
  • Bookmarks, the new app collection. This functionality exists in all mobile browsers today. What is novel is how it is presented in Junior. A separate view shows the open pages at the top and the bookmarked pages at the bottom. The developers discuss (at the 40:00 mark) how they’ve decided to display bookmarks as wide rectangles. This allows us to find the link we’re looking for quickly, but more importantly for the mobile web, this is the new app collection. The mobile web developer can customize the bookmark icon, and users no longer have to type in a URL or remember the name of the app in a list of bookmark titles. This experience is now identical to selecting an app from the native app list.
  • A development platform for nondevelopers. As a developer, I'm most excited by this. Take another look at the bookmark (app collection) view. To create a bookmark, you simply drag an open page to the lower area of the screen. Let’s assume you can drag bookmarks around. With the adoption of web intents/web activities, a user will drag one bookmark (app) onto another, creating a service connection between the two applications, allowing users to create new higher-order apps with no code at all. This type of open app development model will drive the future of the mobile web.
  • Multi-user support. My house shares the use of an iPad, which means that our app icons share a common canvas. Ideally, I would prefer that my boys do not “accidentally” open up the LinkedIn app and start making new connections, but this is unavoidable with small fingers and inquiring minds. Mozilla Junior has a dedicated screen for selecting which user is currently using the device. Combine this with some level of authentication, and you now have true app containers. These could be for parents/kids or consumer/enterprise apps. I hear requests for the latter almost daily.

 Native apps are still great, but the mobile web alternative just got much better. Mozilla Junior has opened my eyes to the future, and I may need to buy some shades.

Comments

Check Adobe PhoneGap / Apache Cordova

There is an alternative to the unlimited funds for native app without loosing the native app.

Adobe PhoneGap (Open Source Apache Cordova) provides an HTML 5 browser packed as a native app. You can use native APIs (GPS, Camera) in a more or less portable way and you can add platform dependent compiled plugins (ex: scan barcodes, etc).

The application is HTML5, CSS and Javascript, hence most of it is platform independent yet it runs locally on the phone (no web server really needed, only for data requests).

Regards,

Jose Luis

Agreed, Hybrid apps are a 3rd solution

I agree and am a fan of what Cordova, Titanium and others provide in the hybrid app arena. I offer these solutions up as a third alternative to pure native and pure web for those that want a nearly-single code base yet also want a presence in the app store and as an icon on the user's device. Having the bookmarks look like app icons within Junior will take one of the value props away from hybrid apps. Libraries that enable javascript/java bridging will also accelerate the move to the mobile web from a position that is currently held by hybrid. But your point is correct, this is also a viable solution.

i second you in this regard

i second you in this regard :)
Facebook Application Development

Mobile Strategy

The most important thing is to make sure that you have a clear mobile strategy. Ideally this should be an agile strategy that can adapt and change over time as the mobile landscape changes so rapidly. In my blog I discuss more details about how to approach developing a mobile strategy and how to decide between native and web on mobile: http://blog.jamesdbloom.com/mobile-strategy/

iPhone Application Development

Good Blog! Thank you so much for sharing this post. Your views truly open my mind.

Facebook and Native Apps

Clients Learn More

I like your info; I am sure about this info can not be easily found from and sources. I think customers or clients learn more and more in this mobile web industry; by the way thanks for sharing info.

Patricia Hall - Mobile Website Design

Business Logo Design

I really need to have or to share this all in one site.It has a total package that you are longing to look for great idea with it and very interesting details ..GOOD JOB for that!