I think we are close to the tipping point where a majority of developers begin to favor webapps to iOS native apps. I've seen this coming a mile away. Apple almost lost a big portion of its development community 2 years ago with that whole 3rd party development platform issue. Apple relented, and they are now turning a different crank with the big subscription tax. They are playing a game of monopoly here. It's the same kind of game Microsoft played in the 1990's and by attrition have lost to the Linux/OSS movement.<p>Apple currently holds one trump card with Safari on IOS devices though. By restricting HTML5 Audio controls, and rendering engine speed, it prevents games and music web apps from being viable inside the browser.
A little OT, but I was actually thinking about the in-app subscriptions policy the other day as it applies to SaaS. I know that there was some email floating around that was supposedly from Steve Jobs saying it didn't apply, but I was curious if anyone out there has had an app rejected (or accepted, for that matter, since the policy took effect) for not accepting in-app purchases of subscriptions. We are thinking about beginning work on a companion app to a SaaS product. The app would be free, but step one is signing in to your account on the SaaS, which is not. There is also no free tier. We cannot afford to give Apple a 30% cut of our subscription price, so we are not planning on offering an in-app subscription purchase option. We would like to include a link that opens a page to the main site in a browser for those who don't already have accounts, although I know that is explicitly forbidden for apps that fall into the subscriptions category.<p>Any thoughts? Just curious what our chances of rejection are for something like this in the current "climate".
If you are't into first class economic writing, and I'm talking so good it almost explains the euro, pick up the FT Saturday edition. Tremendous coverage of books, arts, personalities, and occasionally some truly quirky stories. Also: A "How To Spend It" magazine that takes appalling up to the point of irony.<p>I know, the HN audience doesn't care. But amid all the discussion of platform strategy, the FT staff deserve a salute. There is a reason this paper doesn't need Apple.
We all know how this will go, apple waits six months until it's pissed off the maximum number of people and then it'll reverse its decision or make the terms much more acceptable.
If this is the best you can do with an HTML5 'app' then native apps have a long future. It's buggy, laggy, animations are wrong, graphics are low resolution in places, and user interface widgets are odd and non standard.
People like to talk about black and white, native versus web, etc, but this is simply a matter of finding the right fit for the Financial Times. Many of the newsy apps can be done very well with the latest browsers (and other kinds of apps, too!). It makes sense for subscriptions as well as for maintenance and tech investment, and they won't lose much (if any) functionality. Some apps will always be better suited for native, but as the browser technology grows, we'll move back to web apps more. It wasn't so long ago that touch gestures were pretty hard to do right in a web app, so the only way to do a mobile app right was to go native.
For straight content delivery companies, making a web app should be the first priority. A native app isn't going to offer much in the way of enhanced functionality, and your effort will likely be diluted while you chase multiple platforms.<p>It makes even more sense to focus on a web app when your company already has a web site. You likely already have the expertise on staff to create a good web app, and any new features or techniques you develop can be easily used in both places.
I think a lot of people are missing the bigger picture here, which is Apple is unwilling to just hand over user details, which the Financial Times and the likes want. The 30% cut "gripe" is just what they are telling the public to try to get you on "their" side. If I recall, Amazon actually had (has) a larger piece of the pie for subscriptions, but they are will to give out User Information.
The "HTML5 apps don't cut it compared to native" argument is incredibly short sighted. The pace of development in this area is staggering. Things are moving very quickly and in a short time, the days where HTML applications didn't perform as well will be long forgotten - as forgotten as the days when the internet ran at 2400 baud or when you needed a huge tape to record television.<p>Think of the future, not the present.
Apple is playing with fire, they have built an incredible platform for others to build on top of, but a platform requires a level of trust from developers and businesses in order for them to invest in it. Apple seems to be doing their best to destroy that trust. What Apple's greed seems to blind them to is that while, yes, companies gain a lot by building on Apple's platform, Apple also accrues a lot of benefits just by those apps existing, without having to take a 30% cut.