I haven't tried Flutter yet, but I want to provide my experience of what non-native mobile development usually looks like comparing to native. Through my mobile

I haven't tried Flutter yet, but I want to provide my experience of what non-native mobile development usually looks like comparing to native. Through my mobile development career I have tried C/C++ cross-platform development on mobile, JavaScript frameworks (e.g. PhoneGap), Xamarin and React Native. Cross-platform frameworks always seem attractive because you can write code once and run it on both Android and iOS. When you start development it might also feel productive at first because you finish 80% of the project much faster than with using native platform frameworks. Problems begin when you need to interface with native code or if there are some small annoying issues. You get stuck for hours and days trying to solve something that would take much less if you dealt with native platform SDK. In the end you are not completely satisfied with your hacky solution and it took as much time as native app would take. My opinion is that if you have a very simple app, it might be OK to write it in, for example, React Native of Flutter. But if you have a more complicated app and it's an important part of your business, you should go native.