4 ms·
My larger point was that web apps will take a back seat on the iPad as they have on the iPhone. If you want something that looks great and performs - you have t
by fjabre 17y ago
My larger point was that web apps will take a back seat on the iPad as they have on the iPhone. If you want something that looks great and performs - you have to go through the Apple ecosystem. I think that's pretty clear.
This is in direct opposition to the upcoming Chrome OS netbooks where web apps will be at the forefront and central to the device's operation, being given better access to the GPU and so forth...
- hellotoby 17y agoI actually think that web apps are almost perfectly suited to the iPad. With HTML5's local storage engine and users locked in to Safari* there should be some great innovation in this space. The line between native app and web app may even start to blur with this technology. * I agree that user lockin is usually a bad thing, but knowing the full and unchanging specs of the machine should allow developers to do some really interesting things.
- SamAtt 17y agoJust wanted to add that you can create an icon for a web app that on the home screen and it will look and act like a native application (e.g. the mobile safari tool bar and address bar won't appear).
- GHFigs 17y agoCompiled C on a local device is always going to be faster than JavaScript interfacing with a web site. I don't see what they could be doing that they aren't in terms of performance for web apps.
- fjabre 17y agoYeah true.. It's nice to code once though. I feel immense pressure to make a native app for the iPad b/c it's the preferred method of interfacing with the device for obvious reasons. With the iPhone the pressure is a little less b/c people aren't expected to interact with a web app or any app for hours on end on a small mobile device like that.. For the iPad, a laptop replacement in some sense, users will be interacting with it quite a bit more.