All the issues that are brought up the article could have been avoided by doing a simple proof of concept demo.
We are about to rebuild our Android app in Flutter
Spend a week doing a proof of concept first, so we don't have to read this in six months time.
1) The official demo apps were slow and janky. (hmm, reminds me of Flutter. I don't think these guys will be much happier with Flutter, honestly)
2) It was made by Telerik, the company known for bloated and slow ASP.NET controls. Also, surprise surprise, poor documentation.
Eventually, I decided to make 2 separate iOS and Android apps.
The Flutter web demos are slow and janky on some devices and browsers due to depending on WASM, which isn't universally suppported yet. Mobile Flutter apps are sometimes slow ( e.g. the new Google Pay), but they have no obvious excuse to be ( UI in Flutter is really fast, 60fps all that).