That's been proven untrue with walled garden providers over and over again. Ever see a commercial for an Apple product? Apple has one thing in mind: the farming out of development to tens of thousands of little starry-eyed developers scattered around the world. As long as those guys keep cranking out things that make Apple look good and advance corporate policy, they're there to help both you and the user.

If you want to write inside the walled garden, have fun with it. Providing value to the user is the goal, right? In some scenarios it probably makes sense to develop in that fashion.

But not in every scenario. Don't go into this thing either blinded against using an AppStore or blinded towards using one. The truth is a lot more complex. I could list a dozen scenarios that easily would lead me to choose a stand-alone web app. "Technopolitics" or my personal opinion of Apple has nothing to do with it.

I'd be curious to know what those scenarios are, and whether your choice would actually be user-experience driven rather than based on developer preference or business constraints (such as insufficient resources).

These app stores, the Mac App Store, Android Market, the App Store, they give you very little considering the gigantic margin they take from you. It's almost intolerable. It seems it is intolerable for at least one major enterprise, Playboy.

Apple started high at 30%. If competition dictates, they can lower that percentage at any time.

They're also free to renegotiate a lower rate with specific content producers.

We were talking about the web. If there's a risk of webapps becoming competitive with native applications on the basis of that 30%, Apple is free to lower it.

Given that our clients have been discussing implementing webapps (in addition to their existing Android and iOS applications) entirely due to the 30% issue, this isn't that crazy.

> You may think developers will be more prone to writing apps for the Android exclusively but they won't because they would still be missing out on their 70% revenue from the iOS app store.

I'm not sure what you're basing this on; Android is a rapidly growing portion of our media clients' in-app purchase business.

How much you want to bet when that happens, Apple will release an update for iOS that cripples Safari and takes away some functionality in order to force developers to write native applications.

> I'm not sure what you're basing this on; Android is a rapidly growing portion of our media clients' in-app purchase business.

When you mentioned competition I just assumed you meant developers abandoning iOS and developing exclusively for Android (thus making customers want an Android device more and drive market share away from iPhone). I didn't think the competition you were thinking of was more and more web apps coming up to circumnavigate the 30% cut.

No, the real reason Playboy is going the webapp route is because Apple would never approve the content of the app. Apple knows that the web app experience is sucky compared to native apps regardless of the HTML5 hype. Even after a year passed after Jobs' pro-HTML5 and anti-Flash post, HTML5 still sucks, and Apple seems to be in no hurry except to pay lip service. After all, they have financial stake in native apps being better, especially for subscription based content,

My arguments for using open web technologies are purely based with the end users in mind, it may require some short term compromises in some areas of user experience (performance), but that doesnt mean we arent arguing for the best user experience possible.

The App Store is one tap away. Hundreds of thousands of apps all neatly categorized and sorted a bunch of ways. User reviews right on each listing with an overall rating count that's impossible to miss. One-touch purchasing, or, if free, one-touch downloading. It downloads in the background and can be paused/resumed whenever you want.

So exactly how will open web technologies (existing now, or in the future) be a better experience for users than the App Store?

First, that's now what he said. "My arguments for using open web technologies are purely based with the end users in mind," and "but that doesnt mean we arent arguing for the best user experience possible."

Basically, you want to know this: "So exactly how will open web technologies (existing now, or in the future) be a better experience for users than the App Store?"

In context, it allows app makers to build the apps they want for their customers without requiring Apple approval that could/would prevent said app from being deployed.

Any discussion of iOS development and native v.s. web apps must include the app store and it's conditions. If your app cannot commit to those conditions, then you cannot release an app.

You could ignore the answer, but then you are faced with answering the question: How are native apps a better option for all cases? The answer, of course, is they aren't. Any argument otherwise is being dishonest.

I am not arguing about the user experience involved in using the appstore

- Consistent used experience, the same app can be built for every device, not duplicated (at least) 3 times which will lead to inconsistencies.

- Intercommunication, I can right now, open a web app on my mac, start using it, then send my current screen to my phone

- Availability, I have an app on my phone with my data that works offline, I still want to be able to access thing same thing using someone elses computer / phone.

Thats a few quick ones off the top of my head, we all know the common benefits of web applications, they dont need to be thrown out the window because of some low hanging fruit that can be fixed in the frontend, I mean not having offline access is not a fault of being a web app, it is purely a technical issue that can be fixed on playboys side.

Unfortunately, this also means that every application will offer an inconsistent UX to their users, as there is no adherence to any platform standard.

> - Intercommunication, I can right now, open a web app on my mac, start using it, then send my current screen to my phone

The ability to save state on a server is not constrained to applications running in a browser.

> - Availability, I have an app on my phone with my data that works offline, I still want to be able to access thing same thing using someone elses computer / phone.

You can do this with native applications as well, however, one of the significant market shifts that has occurred is that you don't have to.

Logging into websites from public computers was always a significant security risk and a trade-off between user experience and convenience; it was simply an inefficient solution to the problem of not having your own, locally trusted hardware.

With the introduction of lightweight, high-performance mobile computing devices using always-on internet access, the need to access your Yahoo mail from a 3rd party's computer has all but disappeared for a large (and growing) percentage of the population.

For instance, why would you have to sign in every time? You can easily use cookies or HTML5 database to solve that in Mobile Safari.

Low Res images, too - since when is Mobile Safari constrained in that respect?