Why Flutter 2.2.0 Is Awesome

 


Flutter 2.2.0 is MAJOR minor update

Following the big launch of Flutter 2, Google has stated that it will continue to develop the framework, which is one of their many projects (we all know how most of them turn out).

Because Google wants to leave a mark on mobile cross-platform for good, we don’t need to worry about the future of our framework. Flutter is maturing.

Flutter 2.2.0 was announced at Google I/O 2021. More than 1,000 PRs in flutter/flutter merged. In addition to Flutter Web, we have a new Dart release, new packages, and tool improvements.

Throughout this article, I’ll highlight three changes I think are essential for Flutter developers’ future.

1. Google Cloud now supports Docker and Dart

Docker supports AOT compilation, so we are getting tested and validated Dart images. Dart on the backend is not a new concept. The community has created projects like Aqueduct, Angel, and Jaguar, as well as complex server frameworks.

One language for developing the front end and back end with Flutter could have its huge advantages.

Since there is no division between backend and frontend developers, everyone knows the same thing about the project. There is even some room for components to be reused since we write in one common language.

If we only have one developer (for maintaining the project, for example) that person can easily switch between platforms, without waiting for the backend developer to make the change.

The activity in the packages mentioned earlier indicates that Dart-based backends are not very popular.

Google wants to support that approach with this update. They are even developing a package that allows us to use Cloud Functions in Dart, enabling serverless solutions. Hopefully, this update will prompt the community to revisit this topic.

2. Performance improvements for iOS

There is no production use of this update. The legendary iOS jank has finally been fixed. Flutter is completely useless on iOS because of this, according to many tweets and YouTube videos (for example, this video).

As Flutter developers, we know that the problem with compiling shaders only occurs in a few cases, so we can avoid increasing rendering performance. However, when this happens, it is a serious issue for users, and can in the worst cases force them to uninstall the application.

Caching shaders before the first frame was an idea Google came up with. However, it only worked with OpenGL. Since Metal is enabled by default on iOS, this issue still exists.

We can see from this PR that the ability to warm up shaders will also be available with Metal. Make sure you’re in the dev channel if you want to try it!

From a business perspective, the first user experience is crucial. You can lose users if your application has too long loading indicators, poor UX, or non-performant animations. It’s great to see Google and the community working together on this issue.

3. Appreciation for the community

Google does one thing better than Apple: it notices its community. Organizing social media initiatives is a part of every event. You can send photos to be displayed on upcoming Google events, create your own dash avatar, and use fun Flutter-related filters.

Flutter’s community is an integral part of its development. Community is Flutter.

Flutter lets developers maintain core widgets, they add some popular packages to Flutter Favorites, and they mention some packages in their tutorials!

Google makes you feel like this framework belongs to you, the developers, and not to Alphabet’s shareholders.

In terms of marketing, this is the ideal way to develop your product. The more you engage the community, the more feedback you will receive. Your users are the best testers of your product. Flutter is no different.

We are looking forward to a bright future!
Flutter is serious about these three things, so the days of people wondering when it will be closed are over. We love Flutter at Droids On Roids (we’re experienced Flutter developers), and we’re looking forward to the next updates!

*

Post a Comment (0)
Previous Post Next Post