Last week VGZ op Reis went live. It’s a mobile application for people on vacation, build by me.
It’s the first application I’ve worked on that simultaneously is released on iPhone and Android. Below you can find a (dutch) screencast which explains the functions of the application. It features several phone numbers that can be usefull on vacation, you can save your own phone numbers to it, you can share your location by email, and the iPhone version also allows you to create your own iPhone Wallpaper.
The design of the application was done by the brilliant guys at BUROPONY.
It was a great event! Almost too many people showed up, we got great presentations, some interesting new API’s and good vibes from the crowd. I got to build my first android app (which I hope to publish some day).
Alexander Muse, CEO of Big in Japan, who built Shopsavy gave the keynote. And he took a lot of nice pictures, which can be found at Flickr.
We anounced a contest with some great prizes (which unfortunately I can’t participate in.. This whole morals thing..).
Last year at MWC in Barcelona, I talked with some people from W3C, the web standards body. They asked me why we developped native mobile applications, instead of using the mobile web. For me that boiled down to two things: More controll over the user interface, and using context information not available in mobile browsers.
The first issue is being solved by better touch screens, which make it possible to directly interact with a (mobile) website’s UI, instead of selecting links with a 4 way button. So the only real obstacle against developing just mobile sites is the context information that phones often have, but can’t be accessed from mobile browsers. This part is being solved by new projects, such as PhoneGap.
This approach has several advantages over native mobile development.
More people know web frameworks then native languages such as Objective C, C++ or J2ME, so it’s easier to find people to devellop you applications.
If you want to develop for multiple platforms, you can reuse most of your code. When writing a native application, a lot of work has to be done for each platform. With web framework most code runs on all supported platforms, and can be reused. The only native part is the container (which is opensource).
Since a lot of the code is webbased, it can easily be used for a mobile website version of your application (but without the context that phonegap provides). Or you can start with your mobile site, and build it into an application.
Phonegap also has other advantages over normal mobile websites: Since the resulting application is a “real” application, it has it’s own place on the users phone. He can assign shortcuts to it, etc. Another advantage is that these applications can be sold, making money in the process. Even for free apps the application marketplaces (such as the apple appstore), are a big marketing tool, with over 300 million applications distributed to iphones.
But it’s a good fit for a lot of information-centric systems.
I really believe in the future of mobile webapplications, and phonegap is a great step in that direction. At some point the native browsers in mobile devices will support these context api’s, and the extra layer won’t be nescassary anymore.