Skip and Flutter



  Skip Flutter
Develop in a Single Codebase
Modern memory-safe language
Compiles to native machine code
Platform-native rendering
Platform-recommended toolkits
Efficient memory usage (no added GC)
Effortless platform API access
Support for latest platform UI

Getting a feel for Flutter

Flutter UI Templates

Flutter in the wild

A good litmus test of any technology is to see whether the technology’s creators themselves use it for building their own apps. In this case, Google has indeed built some of their own flagship apps, such as the Stadia and Google Pay. However, the Stadia app – along with the entire Stadia streaming game service – was discontinued in 2022, and the Google Pay Flutter app is in the process of being discontinued and merged into the native Google Wallet app.

The Future of Flutter

Flutter has a large community and ecosystem of support libraries. It is probably going to be around for a long time to come. That being said, Google are themselves very clear on the recommended way to build Android apps:

Case Study:

From Flutter to Full Native: How We Optimized Performance and User Experience for’s Mobile App

You may be familiar with Flutter, an open-source UI software development kit from Google that’s useful for developing cross-platform mobile apps from a single codebase for any web browser. It was released in May 2017, and we use it to develop many of the screens on our mobile app. While this solution worked well back then, today’s users expect more—more accessibility, more performance, more features, more animation, and more innovation.

To that end, about two years ago, we decided to invest heavily in a mobile-first approach to increase the growth and adoption of our mobile app. As we started the research and defined the problem to solve, we asked ourselves: What is the right technology that will help us achieve our vision of being mobile-first while providing a high-performance, native experience? How do we ensure the solution can evolve as the OS ecosystem changes and differentiate our offering from other available products?

We Weighed the Pros and Cons…

Flutter is an excellent technology for building cost-effective, multi-platform native solutions:

However, supporting both Flutter and native versions in our iOS and Android applications was affecting development, production support, quality, and the state of the codebase:

Native development offered superior performance and responsiveness due to optimization for specific OS and hardware.

Yet, there were drawbacks to this approach, as well:

Native Approach Delivers Lightning-Fast Performance

Switching to a fully native approach was a massive effort that took a year and a half to complete, but we can confidently say that it was the right decision. The native approach provides full access to native capabilities and the native ecosystem, enabling us to deliver exceptional user experiences.

Tightening the codebase for improved readability and easier maintenance. There is now less risk of regression issues sneaking into the codebase and reduced initialization overhead for faster screen transitions.

Going native reduced the app’s launch time by 40%, from 2 seconds to just 1.2 seconds. The app bundle size is nearly 30% smaller (280MB instead of 398MB), and the app’s memory fingerprint shrank about 65% (from 450 to 200MB). Ultimately, these changes enable a superior user experience with our mobile app.

“The removal of Flutter from our codebase and going from a hybrid codebase to fully native has resulted in the engineering team being able to confidently build out features that look and feel better,” says Tomdroid Anderson, Staff Software Engineer – Mobile.

Time Savings for Developers

Users aren’t the only ones who benefit from going native. Our mobile developers enjoy time and cost savings and the ability to leverage the latest, most up-to-date features and capabilities of the Android and iOS platforms to enhance and enrich their projects.

Jing Zhu, a Software Engineer who also worked on the project, says the new design is easier to debug and saves the team a lot of development time since they don’t need to build Flutter frameworks and Flutter-related libraries. The table below shows the time savings realized:

  Before going Native After going Native Time savings (%)
Unit tests 20 min, 46 seconds 12 min, 38 seconds 64%
iOS simulator build 24 min, 32 seconds 8 min, 32 seconds 188%
Build release 30 min, 41 seconds 22 min, 29 seconds 36%
Build enterprise 29 min, 3 seconds 20 min, 25 seconds 42%

Additionally, development cycles are shorter, thanks to improved Xcode times. The table below shows how switching to native development has accelerated development times:

  Before going Native After going Native Time savings (%)
Clean Build 2 min, 16 seconds 1 min, 6 seconds 106%
Rebuild 29 seconds 2.5 seconds 1060%
Unit test build 42 min 5 min, 6 seconds 650%

“Removing Flutter from the codebase helps us focus on what each operating system provides natively,” says Fernando Jinzenji, Senior Software Engineer – Mobile. “Our productivity has increased noticeably without the limitations of Flutter, and it’s easier for our engineers to maintain the codebase.”

Plus, the new design is more modern. “We now have consistent theme colors across screens, which definitely make our app look cleaner and more elegant,” adds Jing. “Since more and more Millennials are buying homes, the new design could attract more users to our mobile app.”

Building Better for Everyone’s Benefit

Converting our mobile app from Flutter to all-native was well worth the time and effort invested. Now, our developers can leverage Apple and Google’s latest features and capabilities to optimize the user experience. They’re also saving significant time, resources, and budget that can be reallocated into creating innovative features that delight our Consumers and make their mobile experience with engaging, useful, and impactful.

“We no longer have to feel a certain level of anxiety over the hybrid approach potentially holding us back,” says Tomdroid. “Now we can focus on modernization efforts and enable our team to build out cool new features.”