New post on /r/flutterdev subreddit:
Flutter's Biggest Problem
TL;DR: Flutter development needs to slow down.Hi! I've been working with Flutter for the past year. In this post, I want to address the most important issue that Flutter is facing and give some realistic advice for people who come to this subreddit to look for the answer to whether if they should use Flutter for their next project.To start this post off, I want to say: I'm just as passionate about Flutter as you are. I love Flutter and the infinite possibilities that it brings. However, as I became more and more dependent upon flutter, my frustration levels really started to increase.I get it. Flutter is a cross-platform framework, which means that it is and always will be a "second-class citizen." There's no free lunch in the world we live in. While Flutter enjoys the benefit of letting the developers create beautiful apps with a single yet elegant code base, it comes with a price. Flutter excels at UI rendering. You can make complex layouts easily with Flutter. But when it comes to anything that is not just drawing stuff on a canvas, Flutter may not be as appealing.As you all know, "Flutter" is only a UI framework. It achieves other natives functionalities via plugins. The Flutter community has been awesome. They have put out plugins and packages that provide 99% of the functionalities what you will probably need. However, it's usually the 1% of the needs that aren't covered hinder you the most, because they require FIRST-PARTY work.Feel free to disagree and post your own opinions here, but I think that the Flutter team really needs to slow down and focus on some more quality control stuff. Flutter has been growing rapidly in the past few years. Web support, desktop support, many many more widgets, material design specs... These are all great things, but I think that it is better, for them long term, to focus on fixing the issues that currently exist in the framework and working on offical plugins that provide crucial functionalities. Let me elaborate:Fixing Issues: in every Flutter release annoucement, there is a section about "performance improvements," but the truth is: currently, Flutter animations on iOS devices are extremely janky on first launch. Since the introduction of Flutter's support for Metal, the Skia engine is no longer able to deliver the "Native Performance" as advertised on Flutter's official website. This issue has been present for over 6 months now with no viable fix. The only work-around is to recompile the Flutter engine with Metal disabled and face potential OOM crashes (which are likely to happen). Unfortunately, this is not the only severe issue that the Flutter engine currently has. As more and more apps written in Flutter are entering production, I think it's the number one priority to ensure that they are stable and performant.1st-party Plugins: The current status' of the official plugins are really lacking attention from the Flutter team. Plugins like video_player and firebase_admob, are basically incomplete, even broken. You would think that the first-party plugins are the ones that get the most care, but no. Unfortunately, the team has been very slow on fixing and improving these plugins that provide ESSENTIAL functionalities. Just a few days ago they released the news about admob's support for native ads. "Finally!" you might say, but unfortunately, the plugin is in CLOSED BETA, and they "expect to open this up to a broader audience in early 2021." Personally, I'm glad that at lease there is progress being made, but still, Flutter is leaving many developers unable to monetize with native ads. There are other plugins that provide "native ads" with platform views, but this will cause noticibale lag if the platform views are put into scrollable lists. Not ideal at all.So if you are looking to use Flutter for your next project, there are still time for you. When you finish prototyping and making…