But, there is more to web apps than just distribution. And, there is more to why people want to write for these mobile devices than just the app stores.
If you've been doing web stuff for a while, you may be surprised to find some of us prefer the tools, APIs, and patterns behind native app development -- just as I was surprised to learn some people had legitimate reasons to make web apps. Some of us have investments in native code that we can move over to these devices. Some of us think having at least some code in the vendor's pet API provides a better user experience, and makes you better able to track with their platform as it changes.
I was wrong to think people only went to the web for distribution. Consider that people may not just be on these native mobile systems for the app stores alone.
Maybe it's best to speak as a hypothetical "developer with an idea" that I'd like to hypothesize to be common: I don't have time to become proficient in developing on webOS/Android/iOS, and I don't want to do a half-assed job by quickly learning a system I'm not familiar with, so I'll pick one (probably iOS, because it provides the biggest reach internationally, and because I have the sense that iOS users are more likely to pay money for apps). I'd prefer to make one quality app, though, and ship it to all app stores, and have it degrade gracefully across devices that have one feature or another. Also, a pony. But seriously: I think Adobe's Flash-to-iOS is a great idea, but I have close to 0 confidence in Adobe being able to maintain it & keep it up to date with changes to the native platform. If Adobe had advocated making iPhone apps by shipping a full-featured Flash-to-HTML5 compiler and vocally advocated pushing HTML standards to reaching feature parity with the iPhone 4, it would be a dream come true.
Could you expand on that? I thought it was pretty much all about distribution (deploy to one place and everyone can access it from any machine).
if(device.gps) loc=device.gps.getLocation()
img=device.camera.takePicture()
device.accelerometer.onChange(trackIt)
I absolutely agree with you, and provide a chromeless browser for web apps.
Making software for full-featured mobile devices that degrades gracefully for those with less features is a hard problem, but a very real one for phone developers. The iPhone isn't going to be the extensively polished de facto monopoly Apple dreamed it would be. Developers do want to write cross-platform applications (and no, Adobe doesn't have the right talent to write a solid "higher order platform").