To app or to not app

[PanMan]

Things the mobile web is currently missing:

* Native performance.(getting better, still not there).

* Offline is way harder (possible, with manifests, but harder).

* Monetization is harder: you can't just 'sell' a webapp.

* The appstores (can be) a great distribution and promotion channel.

* The web has way less access to the device: No contacts, camera, etc.

It's getting better, but native apps do have their advantages.

[lecha]

Wait. Why do you have to choose?

What's wrong with the following pattern: 1. build an HTML5 app 2. build a native app that embeds a Web control 3. package the app and HTML5 app together using application cache 4. distribute on AppStore

You get the a) offline support b) monetization c) distribution via AppStore

[mclin]

2. Browser apps when powerful will compete with the apps on the app store.

ie, right now they don't. I don't plan to wait.

[rameshnid]

Patience pays, most of the time.

[tptacek]

Is there any realistic way to do a mass-market GPS-driven app outside of an app store?

[bengl]

If all you need is coordinates, there's always W3C's geolocation API: http://dev.w3.org/geo/api/spec-source.html

[mkramlich]

Postabon's mobile website can access the users GPS location, if that capability is present on the user's device. smanek can chime in here. (I wrote their iPhone app.)

[rameshnid]

Hmm. Don't know if there is an option completely outside of an app store. U can use the app store that Tom Tom plans to enable on it's new gps device.

See http://www.electronista.com/articles/10/04/29/tomtom.to.use....

[JoachimSchipper]

I don't think so, but you can still try to keep as much logic as possible on the web. (E.g. by providing a browser window to your website and a button that does a POST to your API, and nothing else...)

[PanMan]

The javascript location API works since iPhone OS 3 and Android OS 2.