Give it a shot before you knock it, Flutter uses its own Native rendering engine written in C++. It is very fast and responsive.
It might be fast and responsive, but correct it is not. Flutter's widgets don't feel "native"; they feel like someone made a somewhat poor facsmile of the real thing because that's exactly what they are.
When you want your UI to stand out you would anyway move from native look. Flutter is very good for that.
As a user, I don't want your UI to "stand out". I want it to be consistent with everything else, so I don't have to re-learn what a button looks like. For me at least, attempts to do "branding" in this manner backfire big time - I'll recognize the brand alright, but now I have a strong negative association with it.
They are already different on each platform be it iOS android or web. Consistent for me would be same in all platform which would be a browser for most cases.
Yeah, no. I don’t want your UI to stand out, and if it does it stands out for breaking my expectations of how I expect apps to work on this platform. Every platform has a couple of things that are considered “acceptable” to customize (fonts, logos, colors) and things that are sacred and inviolable (accessibility, text editing, system API). Apps that use Flutter cannot tell the difference, and use experience suffers.
Browser apps are not native and users have accepted it. What you abt users experience might be different from theirs.
Not emulated. Painted at the OS level, same as native controls. Uses https://skia.org/. I second the grandparent poster's opinion about runtime speed and developer productivity, but Flutter is still not mature enough for production.
You are correct but I obviously disagree on not mature enough for production, I’m in production with paying users. :)
I'm glad to hear that. Let me know your experiences. We've a customer base of about 0.5 million, and ours is a mission critical system. Which is why I'm currently reluctant to use Flutter, even though I'm a huge fan.
They’re “emulated” in the sense that they are custom widgets designed to mimic the appearance and behavior of widgets from the OS’s native UI framework. They’re fine from a performance perspective, AFAIK, but you run the risk of the replicas imperfectly emulating some aspect of the originals’ behavior and creating an “uncanny valley” effect.
Emulated in the sense that it's a separate rendering of the components versus using the OS's components directly.
You're right; what word would fit something that is not the real deal, but is crafted in a way to be almost indiscernible? Would it be, emu... emula... oh it's just on the tip of my tongue.