Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It also supports JavaScript geolocation, which is (I hope) only the first step towards true device APIs that will give JavaScript developers access to phone functionality such as the camera, text messaging, the address book, and more. I’m assuming Apple is working on all that because it’s the next logical step.

I was sympathetic to Apple's original line about iPhone apps -- that web apps were iPhone apps -- under this same assumption, that over time MobileSafari would get all these capabilities and more.

But those have been slow to materialize, and now Apple is making a bunch of money via the App Store. Why add things to MobileSafari that remove Apple's cut of sales? Or otherwise splinter the billing/in-app-purchasing system? Or confusingly 'duplicate functionality'? The assumption that Apple is a "true believer" in web apps becoming as capable as App Store apps may no longer be safe.

Going strictly by Apple's self-interest, it would be equally valid to predict that Apple may, over time, add various kinds of policy or remote-driven cripple-switches to MobileSafari -- so the web isn't a back-door offering 'inappropriate content' or otherwise competing with the App Store.

Of course Google is a "true believer" in web apps. Any bets on when we'll see a Chrome browser for the iPhone?



Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: