4 ms·
Sorry, but I'd disagree. The transitions aren't very smooth and often times you're faced with a blank screen while waiting for assets to load. I was actually v
by devinfoley 14y ago
Sorry, but I'd disagree. The transitions aren't very smooth and often times you're faced with a blank screen while waiting for assets to load.
I was actually very hopeful that the app would feel as good as native after I'd read about it, but I was disappointed.
- marknutter 14y agoIt may have to do with the hardware. On my iPad 3 it feels exactly as good as native.
- flatline3 14y agoThat hasn't been my experience. "It's as good as native" seems more driven from hope than reality, or more generously, ignorance of the differences that would stick out like a sore thumb to someone intimately familiar with the native platform. I note that you're a web developer. Full disclosure, I work in the native mobile development space.
- marknutter 14y agoI do native development as well as web development. It's easier to get a performant native app than an HTML5 app, no question. But you can create a native feeling HTML5 app that really only the trained eye of a developer would be able to notice the difference of. Most people don't even know the difference between a native and an html5 app. Devices will continue to get faster, and just like on the desktop native applications will be relegated to hardcore apps like 3d games and content creation programs like iMovie, etc.
- kevincennis 14y agoCompletely agreed that a well-optimized native app will outperform a well-written HTML5 app every time. I do think, though, that the difference is getting smaller - especially for apps like Facebook, which are almost entirely content-driven. Things like games are obviously a totally different story. Even five or ten years out, it's hard to imagine HTML5 games with WebGL or whatever seriously competing with native apps.