4 ms·
Tracking is the big one, but depending on the app, there can be performance-related reasons. If your app is graphics/multimedia heavy and you want the interact
by hamburglar 4y ago
Tracking is the big one, but depending on the app, there can be performance-related reasons. If your app is graphics/multimedia heavy and you want the interactions to be seamless and fluid, you really want to be in control of all the threads and resource loading and can't trust a browser/JS-engine not to glitch your buttery-smooth transitions and animations. Or at least, you'll spend a lot more work trying to get it to acceptable. Lots of people wouldn't care about this, but I've worked for some folks who are absolutely rabid about perfecting the UX and sometimes, native is the best choice for that.
Edit: but for real, it's the tracking almost always.