3 ms·
> works well in iOS Many people would disagree with you.
by dvfjsdhgfv 5y ago
> works well in iOS
Many people would disagree with you.
- rektide 5y agoHard to assess how much of this is Google's fault, or anything that can be dealt with by anyone. Do folks have some examples of non-native iOS platforms that do have flawless no-lag 120Hz display?
- Dylan16807 5y agoAre you proposing that iOS might be so broken it's impossible to flawlessly copy a handful of screen-size rendering buffers at 120Hz? Because if you can do that, then it's possible to make a flawless no-lag non-native 120Hz UI.
- nexuist 5y agoI don't know if you can even access the screen at such a low level on iOS, I think for sure you'll have to go through a middleman to get pixels on the screen.
- Dylan16807 5y agoSure, you have to go through a middleman. Does the middleman stop you from copying a texture to the screen?
- GekkePrutser 5y agoIt shouldn't be non-native, that's the problem. The best apps are always native ones. They make the most of the available APIs, fit in the OS the best both graphically and technically, and are the fastest. If it has to be cross platform, something like React Native which leverages system controls would be a better approach than flutter which draws its own controls. But even there you will have to deal with a lot of translation due to it being JavaScript.