[rohansingh]

As someone in a similar position as the OP, I definitely recommend Flutter. I'm working on a new hardware startup, and my team has strong backed and infra experience.

That jives well with our product, but we do also need a mobile app to interface with the product. Flutter has been great in this regard. Dart and the declarative UX framework are very grokkable for backend folks.

The UI/UX is definitely good enough. Our app feels native, is snappy enough to get the job done, and looks way better than the native Android app we were trying to build before. Even if we were to have to go fully native down the road, Flutter is just the right tool for the job of getting us off the ground.

For a small team, there's just no way we could build both an iOS and Android app separately, on top of hardware, firmware, and a backend. It would kill us before we ever even launched.

[saagarjha]

> The UI/UX is definitely good enough. Our app feels native, is snappy enough to get the job done

n.b. to you.

[latchkey]

Sure, but they are correct and you're focused on the premature optimization.

I've also built a small flutter app where everything runs snappy and it more than solved the needs with a minimal development time and number of lines of code.

[saagarjha]

If you’re happy and your users are happy with Flutter, go right ahead with it. But please don’t be the all-too-common startup that writes blog posts about their “coding velocity” with Flutter (of course, they can’t afford to hire talent for anything else) while they keep their fingers in their ears as users scream about usability or missing platform functionality.

[latchkey]

My users have no idea it is flutter, that is the best part.

[saagarjha]

Then you’re probably fine :) Do make sure to keep your eye on this, though, just like you might be a bit more regular when checking the performance of a Python application.