(Mobility != Mobile Internet)!!!
Thursday, October 18th, 2007One of the overall themes at Mobile 2.0 was some people saying “the browser is the most important thing to pay attention to in the future development of mobility.” Which was normally followed up by someone else saying “Hey! Mobility isn’t all about just making the web mobile.” I’m not sure that the common ground there was ever really found, despite the fact that both sides had only slightly different takes in reality.
The “browser is the most important thing” folks don’t want to just take the normal web and jam it down. They’re also interested in how to expose device native functionality to browser based applications. It’s not that what browsers do today should be the only way we interact with mobiles, but that the patterns, models, and methods that have made web based applications rapidly evolve would be great to emulate in mobile. That doesn’t mean that other methods of mobile development don’t exist, or that all the mobiles should be are scaled down web browsers. But that the best way to grow the ecosystem and find the fantastic mobile applications is to crack open the development model the way the web has gone.
And just because the browser is the most important thing that doesn’t mean that all of mobility is about making the web mobile. “Most important” does not mean sole and only area of possible improvement. Sure, there’s plenty more to mobile than the web. But the web makes interesting things happen cause it’s built on standards that are for the most part beyond the control of manufacturers, software vendors, and carriers. Access to address book/contacts functions was something that came up over and over, some folks even started kicking around the idea of forming some kind of alliance around standardizing open access to contacts. Even if the browser isn’t the way to standardize access to these functions, I think the web could provide the model for how to get to a standard when we don’t already have one.
