Yes. There's also icon "packs" that mimic the iOS style, and I believe you can use different icons for different builds between android and ios?
back
2 comments
I wouldn't call it "native" when you bundle half an OS worth of libraries with your app, including one that draws the UI with OpenGL instead of using system anything.
Nowadays folks like to call "hybrid app" as "native app". The bottomline is "native app" is what allowed to be listed on the "app store".
I think I've seen electron apps in macOS app store? And I've definitely seen all kinds of webview-based apps on google play.
I wouldn't call it "native" when you're running a sandboxed app on top of an immutable base system, but our goalposts tend to change pretty frequently in the arena of consumer electronics.
Flutter is not native. They draw all the controls themselves, so there'll always be some difference between how the native platforms feels and how a Flutter app feels (due to small and not so small differences).
Their renderer is why I love and hate Flutter. It's so easy to become productive in Flutter, but the end result always feels off-brand on every platform.
I suppose the exception is the web, where React-based rendering and CSS resets have killed off most of the native feel anyway, but Flutter on the web is too slow to actually be usable in my experience. Yes, with a high powered laptop and a JS-optimized browser like Chrome it's acceptable, but that just shouldn't be necessary.
I can see Flutter have its advantages, like on Fuchsia where "native" isn't defined by anything else and on kiosk systems where the application is the only meaningful UI that'll ever be shown, but in apps I'm just generally annoyed by its seeming popularity.