4
3 Comments

Flutter goes 1.0: Anyone using in production?

Flutter - Beautiful native apps in record time

My company is toying with the idea of shifting over from Xamarin.Forms to Flutter for new projects. We've done some proof of concepts and been really, really happy with the dev experience. The iteration and coding speed is so much faster than anything I've come across for mobile development.

Anyone else here using (or looking to use) Flutter? If so, what are some pros / cons that you see?

The biggest con we've come across is the lack of ecosystem around some of our core needs like bluetooth and mapping. Though it looks the story for most of these areas is rapidly improving.

  1. 1

    Recently, I had an idea for an app and during my research for a cross-platform solution for making mobile apps I came across Flutter, and I've spent the past week or two reading every article and watching every video I can get my hands on regarding Flutter.

    In regards to the pros, there are several but to name a few, I see that it is very fast to prototype an app which is ideal for makers trying to get their apps in front of people pretty quickly to validate their ideas.

    For the cons, since I'm coming from the web I found it very slow to design layouts at the beginning and it needs some getting used to and you need to rewire your brain to how you should approach making layouts, the other con I came across which you have mentioned is the lack of ecosystem especially when it comes to state management, I still can't find some resources that explain the BLoC pattern very well.

    1. 1

      State management has been a bit confusing to us as well. I see folks recommending the BLoC pattern but it seems strange coming from a Xamarin.Forms and MVC web world. As someone unfamiliar with a lot of the reactive / stream terminology it has definitely been tough to grasp.

      I have seen some decent videos but I tend to prefer text tutorials... and have yet to find a good explanation.

      The Scoped Model package does appear to be a simpler state management method to understand. But I hesitate to go all in on it since the community (and the Google team) seem to be rallying around BLoC

      1. 1

        I agree with you about the Scoped Model, and it is what I have decided to use, for its simplicity and because the app I'm planning to make is not complex, in case it gets traction I might then consider moving to the BLoC pattern if I fully grasped it and if the app needed to, otherwise, I will stick to the Scoped Model for the time being.