3 ms·
twice the cpu kills the battery on mobile/tablet => it is harming user experience. Instead of trying to be native in a browser just be native on the plateform
by camus 13y ago
twice the cpu kills the battery on mobile/tablet => it is harming user experience.
Instead of trying to be native in a browser just be native on the plateform you bring the product. The web is not good for everything.
- jasonlotito 13y agoNeither is native. And frankly, if your app is actually worth something, you should have a web version. Not everyone can afford a shiny new iPhone. And that does a thing far worse than harm the UX. It prevents those that would benefit most from using the app. You make it seem like the battery life is the only thing that matters.
- wpietri 13y agoDepends on how much CPU you're using. Any app that is using a lot of CPU on a phone will kill the battery regardless. So I agree that if you're doing something where using 2x CPU will make a significant difference and you've already optimized things heavily, then sure, go native. But I'm sure that most apps on my phone are already using 2x the CPU they could be, and I just don't care.