Because this one is here to stay.

I’ve been looking for hybrid mobile solutions for some time now without learning Android (Java) or iOS (Objective-C). As a backend developer, I wanted a practical solution with pleasant documentation and a relatively low learning curve.

As I’m not a big fan of creating components from scratch, I was also looking for a set of ready-made components that were highly configurable and, finally, that were also performative. It wasn’t too much to ask, right? I was looking for something that every programmer wants when they are going to know something new.

The big problem is that all the solutions I found along the way only partially solved the requirements. In general, the solutions always had some weaknesses in terms of performance and native experience (as was the case with options such as WebView or Bridges).

The challenge was on, and I was excited about the discoveries I would make in the process. And yes, of course, I thought of React Native! I’ll come back to this point yet, but I want to tell you better about all my journey with Flutter in this post:

The encounter with Flutter

When I met Flutter, he was already 1 year in Beta, but without a 1.0 version.

I was surprised to find that, even in Beta, there were already some apps in production. There were few, of course, but they already had several animations and features essential for a great app in production.

If you don’t already know, Flutter is supported by Google. This call made me feel firm (“this one is here to stay”), especially after Google invested heavily in marketing, tutorials, and Flutter’s own development team.

Another curious point about Flutter is the Dart language , which is a language created by Google in 2011. At that time, most programmers had never heard of Dart — — and I include myself in that list.

This Dart language thing was my first hurdle with Flutter. Anyway, I decided to go deeper and follow. It’s worth sharing with you what I learned.

#programming #apps #javascript #flutter