3 ms·
Native UI toolkits (with “native” defined as system standard) have system hooks and access to functionality that third party toolkits don’t. Not sure about Andr
by kitsunesoba 7y ago
Native UI toolkits (with “native” defined as system standard) have system hooks and access to functionality that third party toolkits don’t. Not sure about Android but on iOS I’m pretty sure that a Flutter app would have a battery impact closer to that of a 2D game than a traditional app, even if it’s reasonably efficient.
- skybrian 7y agoGames tend to animate all the time at 60 fps. That drains battery. Flutter is more like a regular UI in that it animates, but stops when idle. Though you could write a game in it.
- jcelerier 7y ago> Native UI toolkits (with “native” defined as system standard) have system hooks and access to functionality that third party toolkits don’t what makes you think that ? the time when scrollbars were rendered in-kernel is long gone.
- saagarjha 7y agoI believe the current situation is that first-party toolkits have much more insight into the OS and underlying platform than third-party developers can afford.
- jcelerier 7y agoAnd I don't think that this is true. First party toolkits do the very same GL calls in the end than a third party would.