It's been a while since I knowingly tried a Flutter app. Most of the ones that I have used even temporarily are Google garbage, and they are so bad that I will not give any Flutter app another try. I also fundamentally think that the technical approach of Flutter is wrong and should be resisted. You now not only have the "build platform lagging system platform" problem (something that happens to all non-native development options), but you have to trust that the Flutter people understand the target systems well enough to make the "draw" work (I think they fail every single time, just like Swing with its "windows" or "mac" personalities did).
But platform appearance is the thinnest layer (and Flutter can't even get that right because of its model). Design is about how something works (and a little about how it looks). Flutter apps don't look like iOS/macOS apps, but more than that, they don't feel like iOS/macOS apps. Flutter apps on the web will never feel like a proper web citizen, because they aren't — they're either a single canvas or a lot of canvases that have to have accessibility hacks instead of building on the platform.
If Flutter as a system decided to take the Swing approach of having its own "native" look and feel (https://www.geeksforgeeks.org/java-swing-look-feel/), I would not expect Flutter apps to conform to the high standard that I’ve expressed here. But the moment that they said "we can do better than Apple with the Cupertino personality", they failed — and IMO so does everyone who uses that.
(We had someone at work try to push Flutter as a cross-platform, including web, engine a couple of years ago. It was a complete disaster because he didn't know Flutter, didn't know Dart, and wasn't actually very good at architecting anything in the end, either. His React apps were nearly as bad. It took someone less than three weeks to rewrite the demo app from Flutter — which took 2 people ~6 months to build — to React Native and it did more, more smoothly.)
But platform appearance is the thinnest layer (and Flutter can't even get that right because of its model). Design is about how something works (and a little about how it looks). Flutter apps don't look like iOS/macOS apps, but more than that, they don't feel like iOS/macOS apps. Flutter apps on the web will never feel like a proper web citizen, because they aren't — they're either a single canvas or a lot of canvases that have to have accessibility hacks instead of building on the platform.
If Flutter as a system decided to take the Swing approach of having its own "native" look and feel (https://www.geeksforgeeks.org/java-swing-look-feel/), I would not expect Flutter apps to conform to the high standard that I’ve expressed here. But the moment that they said "we can do better than Apple with the Cupertino personality", they failed — and IMO so does everyone who uses that.
(We had someone at work try to push Flutter as a cross-platform, including web, engine a couple of years ago. It was a complete disaster because he didn't know Flutter, didn't know Dart, and wasn't actually very good at architecting anything in the end, either. His React apps were nearly as bad. It took someone less than three weeks to rewrite the demo app from Flutter — which took 2 people ~6 months to build — to React Native and it did more, more smoothly.)