Hacker News new | past | comments | ask | show | jobs | submit login

Rewatch the video, it's more than just a shortcut.



Yeah, I'm referring more iOS. I think the idea of "webapps as a first class citizen" is a bit of a red herring. Web apps will never be first class citizens (especially not on a phone) because they fail simple performance tests. I think what OSs ought to aim for is what Android does, a smooth integration of offline and online modes.

Ubuntu does this somewhat, iOS not really at all (though it is successful in the way you speak of), but I feel there's a combination of the way Adnroid, iOS and Ubuntu are doing this that could hit a sweet spot.


I think you're being short-sighted. There's nothing inheritantly different about mobile that prevents web apps running as well as they do on the desktop. You are aware that on the desktop JavaScript engines like V8 can keep up with any garbage-collected language, right? There are a few reasons why things are progressing slower on mobile, among them:

1) There is very little browser competition on mobile. Users are either unaware of or don't see the benefit to downloading an alternate browser, and as a result the OS vendors have less of an incentive to improve their browser rapidly. On the desktop browsers like Firefox and Chrome release a new version every few weeks, whereas on mobile the OS vendors release once or a twice a year.

2) The JS engines haven't been optimized for ARM as heavily as x86. We'll get there though.

These are very much short-term problems. And despite that, you can write performant mobile web-apps today. If you have an iOS device you should try out the game X-Type: http://www.phoboslab.org/log/2012/06/x-type-making-of which is written by a fellow HNer. It is extremely snappy, even when played without the assistance of Nitro.


I have a couple of responses:

1. Who wants to write complex programs in JS? I mean, it's OK and all, but it's messy when you can be writing native apps. I remember the iPhone being all about the webapps when it came out, but native apps ultimatly won.

2. Internet access is still not widely available. On Sprint, where I am, it sucks. If I'm out in more remote regions (which is part of mine and many others jobs), it's gone. Or if I'm in a tunnel on the train, or an elevator, or in my bathroom at work, etc. Or you're on AT&T, have capped bandwidth, etc.

No, we need apps that have a smooth offline to online transition. Maybe web apps will make it there, but I feel we're far enough away that I still like Android's approach.





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

Search: