> Our reaction time is ~200ms, we don’t need 100ms.
Our reaction time doesn't matter when it comes to the look and feel of an application. You can clearly feel the difference between an old DOS computer with a CRT putting characters on screen nearly instantaneously and a modern text editor having a whole UTF-8 rendering pipeline to deal with first.
We've all slowly been growing accustomed to these high latencies and the bar of acceptable performance has been lowered, but that doesn't mean such latencies don't matter.
Personally, I find browsers noticeably less responsive unless developers go out of their way to reduce latency and overhead. Leveraging things like CSS animations makes a huge difference because even on slow hardware they feel snappy, but there are many other optimisations that you need to get the job done.
That said, if the web version was already reasonably fast then I don't see a problem with porting it to mobile
If a mobile browser can operate a website with tolerable performance, then why not stuff it into a platform native webview and he done with it. You'll be fighting the terrible built-in browser engines of your user's devices (I've seen people refuse to update the Webview on Android because they don't know what it is) but your app just got a whole lot tinier and easier to update.
It would probably work the other way around just as well (Flutter to web, or maybe even Kotlin Multiplatform to web and iOS, I haven't tried the latter) if your port source is of good enough quality.
Reaction time and perception are different things not sure why author mixes them.. as a gamer having a ping of 14ms vs 90ms literally ruins competitive gaming. Pro players actually switched countries and cities to have better ping. Heck even getting a keyboard with less travel distance for each keys make a difference, just like how getting a mouse that has response rate of at least 1000hz. I have gone from typical desktop user to hardcore gaming user and each time latency improved it has helped by kd ratio directly. Even 5ms gains matter because worse case scenarios become less worse.. I notice everything above 20ms, but I used to not. One day I bought 140hz monitor it felt little better but not ground breaking I was almost disappointed. But then a week later I got to look at regular monitor, it looked like it was lagging constantly... Now I don't use my laptop because it looks so laggy now. I got used to faster frame rate.
Our reaction time doesn't matter when it comes to the look and feel of an application. You can clearly feel the difference between an old DOS computer with a CRT putting characters on screen nearly instantaneously and a modern text editor having a whole UTF-8 rendering pipeline to deal with first.
We've all slowly been growing accustomed to these high latencies and the bar of acceptable performance has been lowered, but that doesn't mean such latencies don't matter.
Personally, I find browsers noticeably less responsive unless developers go out of their way to reduce latency and overhead. Leveraging things like CSS animations makes a huge difference because even on slow hardware they feel snappy, but there are many other optimisations that you need to get the job done.
That said, if the web version was already reasonably fast then I don't see a problem with porting it to mobile If a mobile browser can operate a website with tolerable performance, then why not stuff it into a platform native webview and he done with it. You'll be fighting the terrible built-in browser engines of your user's devices (I've seen people refuse to update the Webview on Android because they don't know what it is) but your app just got a whole lot tinier and easier to update.
It would probably work the other way around just as well (Flutter to web, or maybe even Kotlin Multiplatform to web and iOS, I haven't tried the latter) if your port source is of good enough quality.