Well Flutter does provide for a way to call into existing native code so I think that mitigates the code-reuse concern. The other thing to consider is that this advantage of code reuse was never realized to iOS. Writing apps for iOS & Android always meant having a C/C++ core with platform-specific shims; J2Objc more recently let you write it in Java but again that just lets you write the core in Java with 2 platform-specific independent frontend implementations. A lot of developers just wound up writing the app twice & shifting as much logic server-side as possible (which hurts battery too). This is the first time you can write the app once & run on both iOS & Android. AFAIK Dart is also only a requirement for the front-end. You are still free to use whatever language you want for your business logic. I'm not 100% clear yet on how good the bridging story is but I suspect it's not bad.