For whom? Product owners who are making a decision about the tech stack for their new startup venture
Flutter is eating the mobile world. This is currently one of the major cross-platform solutions to develop apps not only for iOS and Android but also for Desktop and Web applications (with its limitations) from one codebase. What does it mean for the business? Flutter has a great impact on how all customer-facing digital products will be delivered. Yet, this is not a silver bullet for all business applications and you must be aware of its potential and limitations to include Flutter in the tech stack of your new venture.
This article is based on our experience from setting up the 15+ Flutter Devs Team and building 20+ apps in Flutter. Some of our earlier conclusions have been summarized here: https://leancode.pl/blog/lessons-learned-after-making-the-first-10-commercial-apps-in-flutter.
Flutter has been originally developed by Google as a UI framework for building the apps without the burden of adjusting the interfaces for the multi-screen, fragmented environments running on the different operating systems. This great promise could be delivered mostly with Dart, the programming language optimized for multiple platforms. Thanks to Dart implementations not only the mobile apps developed with Flutter are using hot reload (so that they can instantly look at the results), which greatly streamlines the development process, but also they are compiled into native applications which vastly increases the performance and provide a lot of space for advanced animations and beautiful interfaces. This unification allows the designers to take the best of two worlds and adopt either Google’s Material Design or Apple’s Human Interface Guidelines or even develop a fully custom user interface different for both of those if needed, depending on what is best from the end-user perspective.
As a result Flutter enables developers to build native apps for mobile devices running iOS or Android as well as for Web, macOS, Windows and Linux platforms from one single codebase.
Although the Flutter project has been revealed to the public in early 2015, its first stable version has been announced at the live event in December 2018. It was possible to build commercially successful apps before that date (we’ve started our first commercial project in June 2018), which only proves that Google itself was from the start very cautious about the framework quality. It is still the case, as the major goals for 2020 were to further enhance the Cupertino library and iOS fidelity in general and provide better support for the long tail of extraordinary Android devices. This means that the foundations for further growth and creating the tool for making the beautiful and fast apps fast are solid.
Flutter as a framework has its core components being developed by the Google Team and there are pros and cons of this situation. On one hand, this is a tech giant, fully capable of building all necessary elements and developer tools. Yet, on the other hand, there is a risk that the project will be suspended because of the lack of compliance with Google’s strategy in the long term. Truth to be told, Google is doing a great job to prove otherwise. First and foremost, Google is transparent about the development roadmap at least one year ahead and the community voice is taken into account while making fixes and improvements. Secondly, the Flutter Team managed to convince other internal stakeholders to move their businesses to Flutter and those are really big deals. Starting with Stadia, Google’s gaming platforms which mobile interfaces have been built in Flutter for iOS and Android, through Google Pay major Flutter replacement being rolled out in India and South East Asia in 2020, to Google Ads.
Those are major brands managed by Google and it would be extremely hard to take a step back from such a growing commitment, especially as the new Flutter releases have positive reviews (check our review of the latest release of Flutter 2.0). Last but not least, Google’s long-term goal is to launch Fuchsia, the open-source capability-based operating system whose UI and applications are running on Flutter. It is intended to run on all kinds of mobile and desktop devices with a clear potential to disrupt the market.
Google is not the only source of market credibility for the product. Equally important is community support. Since the days it was born, Flutter attracts developers who highlight the ease and speed of development of even advanced and demanding interfaces. What is more, there has been an outburst of independent libraries created for Flutter and developed by enthusiasts who are all willing to support the framework. It is exceptionally important that those initiatives are coming from the community with some of the most notable gatherings and meetups like Flutter London, Flutter Berlin, Flutter Paris, Flutter Warsaw, and Flutter Chicago which managed to thrive even despite the pandemic.
As a result, the number of stargazers on GitHub has been growing steadily over the last couple of months making Flutter the most popular cross-platform framework in the world. This popularity transfers over time into higher probability of finding new, suitable candidates for the further development and internal maintenance of the mobile app.
Source: Star History build by @tim_qian
Together with the rise of Google’s involvement as well as the community's positive impact Flutter is further strengthened by the examples of new great applications being developed by independent teams. They are coming from different backgrounds, with startups and disruptors like Realtor, Reflectly, EasyA, and Virium through mature digital players like Groupon, Baidu, Alibaba, and Tencent, to corporations like Philips, BMW, Nubank, or ING. At LeanCode we have gathered the experience from building close to 20 apps, some of them described in our Flutter portfolio and soon we will share with the world probably the biggest ever app written in Flutter.
Source: Flutter Case Studies at Flutter.dev
All in all, we can see that Flutter is a solid, credible technology, with many successful implementations and a firm place on Google’s strategic roadmap. Once the obstacles are eliminated, let’s focus on the potential gains from using this technology.
All benefits are worth considering from the business perspective to understand how they help to create better products quicker. Back in the old days for the MVP of an application similar to Uber Eats or Wolt you would need to prepare the following separate apps/interfaces:
In total, those are 8 independent interfaces, which require separate teams and are time-consuming. With Flutter, it is possible to reduce that number to only 4 apps:
Let’s have a look right now at the numbers and costs to understand how this transfers to building MVP for a similar product.
An important disclaimer. The complete replica of the Uber Eats interfaces is not feasible to accomplish during 530 MDs nor 260 MDs with Flutter or any other close equivalent. Yet, an MVP, which is providing 80% of customer-facing features is perfectly achievable within this budget.
From this example, we can see that the time needed for producing the same MVP using separate apps and Flutter is ~51% smaller. This allows not only to streamline the time to market, which is extremely important for the new disruptive ventures but also substantially cuts the costs without any loss on the quality of the final product. The total savings can differ depending on the location of the development team with the average hourly rate between $60 for the USA, $40 for CEE, and even $25 for India and south-east Asia.
What is more important than the instant savings are also the lower costs of recruiting the team needed for the maintenance, as only one core technology is required. With Flutter being the core technology, an in-house developer can coordinate all the issues reported from users for all platforms. For the companies, which decided to follow the separate, native-only interface policy, this in comparison would mean that they need to employ at least 3 independent developers for Swift, Java and React (or equivalent) for support. This means that the difference of the Total Costs of the Ownership will further multiply in the long run.
Not only the costs but also the quality of the product can be substantially improved. Although this is hard to provide quantifiable proof, the team spirit is higher when everybody is united, working together on specific user stories, instead of focusing on the independent, platform-related silos. Experienced product owners understand the burden of coordinating the speed of development between iOS, Android, and Web teams working on the same feature and waiting with the deployment till the time when the slowest team is ready to go forward. From the perspective of project management, this also means one backlog, one design code, and less testing required. These project management benefits can enlarge the potential savings related to Flutter app development.
All in all, the Total Cost of Ownership of the Flutter application depends on the scope of the project and the location of the development team. In your own estimates, you need to include the three independent areas:
Those three saving areas can result in hundreds of thousands of dollars attributed to your future MVP. For detailed estimates on your product please contact us to arrange a scoping call or send us your brief.
Don’t waste these savings. Start working on your Flutter app with us.
At LeanCode we have a team of 15+ Flutter Developers working on remote projects from California, Arizona, the East Coast, the UK, Germany, China, and Australia. We’ve been developing commercial apps in Flutter since June 2018 and have accumulated great experience and best practices. With our team you can benefit instantly from the important know-how on:
It depends on the state of your current applications but this is the universal guideline that works the best:
Don’t hesitate, arrange a free call with us to discuss your brief or project idea.
No reviews yet!