Flutter vs React Native Development: A Business Perspective
There’s a new player in the multiplatform mobile development town: Flutter. Here’s how it stacks up against Facebook’s React Native from a business perspective.
- Flutter vs React Native Development: A Business Perspective
- The Showcase: React Native vs Flutter
- React Native
- How Many Platforms Are We Talking Though?
- Entry Threshold for Developers. Learning Possibilities. Community
- Testing Support
- App Architecture and Prototyping. UI Controls & GUI Elements
- In conclusion
It’s easy to get the appeal of cross-platform mobile development, whether you’re a business executive or a developer. Instead of having ‘two of everything’, that is, separate apps for iOS and Android, you get one team, predominantly one technological stack, shared and reused code between the platforms, and a drastically shortened development time.
Saving time and resources sounds great, but which of the many popular frameworks to choose? There are Xamarin, Qt, Ionic, and many others, all with their own pros and cons.
Today, we’re comparing one of the dominant frameworks in the cross-platform mobile development world—React Native, and a rising star on its way to peak hype—Flutter. Learn what’s common and what’s different between the two, as well as their selling points and bottlenecks, and decide which one will work best for your future multiplatform mobile app.
The Showcase: React Native vs Flutter
Here’s a brief overview of the technologies and companies behind React Native and Flutter:
Well-established, reliable, and popular with developers and enterprises alike, React Native has been used to create the current versions of Facebook and Instagram for iOS/Android, as well as Uber, Pinterest, Skype, Salesforce, Walmart, Wix, and many other cross-platform mobile apps.
It should be mentioned though, that some high-profile enterprise users, like AirBnB and Udontry, have been moving away from React Native in recent years, opting for native app development instead.
This one is a relative newcomer among multiplatform development toolsets, yet is already considered by many to be one of the best. Flutter apps are written in the Dart programming language.
After a year-long beta testing, the framework was officially released by Google in December 2018, quickly becoming extremely popular as the new ‘it’ thing with developers.
As of late 2019, the commercial portfolio of the framework is a work in progress. Still, less than a year since the first stable release, and Flutter has already got the apps for Alibaba, Tencent, Nissan, the University of Toronto, Reflectly, and others under its belt. Some of Google’s own apps, like Ads and Greentea, have migrated to Flutter, as well.
How Many Platforms Are We Talking Though?
On paper, Flutter and React Native come surprisingly close in the ‘multi’ aspect of the multiplatform development. In addition to the two dominant mobile platforms, Flutter also covers development for Windows, Linux, macOS, web, and the soon-to-be-unveiled Fuchsia. React Native is just a little behind, with React Native for Windows already announced in May 2019, along with established plans to expand to macOS in the near future.
However, if you’re looking to cover ground beyond iOS and Android apps right now, React Native is still likely to be the better choice. Why? Let’s examine the current state of both frameworks, platform-wise, a little closer:
- Stable Android and iOS support
- Relatively stable macOS support
- Support of web, Windows, and Linux either at the preview and development stages still
- Stable shared development for mobile and web
- A long history of successful commercial projects, with additional platform- and hardware-specific options coming soon
Currently, React Native stably covers mobile (Android, iOS) and web (although there are some gaps and limitations still), which means everything that’s able to run a browser. All the while Flutter is just gearing up to do the same, with many developers considering it not being production-ready just yet. The state of things will likely change in a couple of years, but right now if you’re looking to realize your own project in enterprise mobile application development, React Native is the way to go.
Entry Threshold for Developers. Learning Possibilities. Community
All of the above means a relatively low threshold for new adopters, toolsets for any occasion, and ease of development thanks to a massive corpus of already solved problems. For employers, it also means vast ‘hunting grounds’ allowing them to quickly hire complete teams of seasoned professionals.
How does Flutter fare in comparison? Both the framework and its language (Dart) are much younger and less popular technologies. Despite the substantial push from Google, its fast growth in 2019, and generally positive reviews from the adopters, Flutter hasn’t yet been around enough to provide for all things React Native has figured out. Flutter’s highly comprehensive documentation and shallow learning curve are impressive though, even if they’re yet to fill many gaps to become truly universal.
As of now, finding a team of tried and tested Flutter developers, especially with any sort of related enterprise experience, can pose a problem. Things can change, and sooner rather than later, but in 2019 React Native wins over Flutter, if by a narrow margin.
When choosing between open-source cross-platform development frameworks, the tech-stack considerations should still be a priority, including a comparison of programming languages and such factors as the ease of finding existing developers and training new ones.
QA and testing are huge parts of any software development cycle. Both Flutter and React Native offer testing options, yet this is where Flutter outshines the competition: it has baked-in features to both run app tests on various levels (unit/widget/integration) and automate them, as well as options to test UI widgets. Google’s Flutter testing documentation is extensive and of a very good quality.
While there are several unit-level testing frameworks and other options for testing in the React Native world, the support is lackluster in comparison to Flutter. There are no officially supported integration and UI testing tools, and much less care and thought put into testing processes and opportunities.
All in all, this round’s clear winner is Flutter.
App Architecture and Prototyping. UI Controls & GUI Elements
Both React Native and Flutter position themselves as frameworks to create natively compiled apps, and there is much truth in it. But their approach to building UI is fundamentally different.
To build interfaces, React Native uses system UI components, while Flutter has its own widgets for it. Where React Native provides a “wrapper” for native, platform-specific UI components of Android and iOS, Flutter essentially creates the elements itself, using the third-party 2D graphics library Skia for drawing them from scratch each time.
The advantages of Flutter’s approach are in the details: developers have two sets of widgets for Android and iOS—named “Material” and “Cupertino” respectively—and can create custom widgets as well as customize the existing ones.
It also means that Flutter avoids one of the main limitations of React Native (and of many other native-component GUI builders for that matter). Namely, the problem of using platform-specific native GUI components of iOS or Android when there are no direct analogs to these components in other platforms.
Where React Native has to either work around such elements or abandon them completely, Flutter just creates the 100% same thing for iOS and Android with no hassle. While this potentially can lead to some inconsistencies in the overall style (like iOS-looking elements in Android apps), it still means less UI testing is necessary, since this is where Flutter’s got you covered.
Flutter was created by Google, so, naturally, Android components are very well-supported and prioritized. However, iOS widgets can be somewhat lacking, especially when it comes down to legacy design, staying behind iOS updates, guideline compliance, and visual consistency.
New iterations of iOS and Android roll out every year, which means UI changes. Flutter’s GUI building will inevitably have to play catch-up or risk making the apps created with it look dated. Striving for a native look as much as possible will come at a cost in terms of more complex code and additional development time, while the results might still not be 100% on the money in the end.
Still, Flutter shows great capabilities in quick prototyping and showcasing, and like React Native, it has the hot reload functionality. Allowing to quickly evaluate the impact of code changes visually, hot reload dramatically speeds up UI testing, which would otherwise take much longer.
In short: if having 100% native UI elements is crucial for your cross-platform development project, React Native is the right choice. If a lot of flexibility at the expense of some ‘nativeness’ is preferable, Flutter is the better option.
When talking about enterprise cross-platform app development, there’s always a choice to be made. Is native always preferable when budget allows it? AirBnB, Udontry, and Dropbox executives clearly think so. Is it better to use a somewhat limited but well-established and solidly backed framework? Facebook would urge you to say yes. Are you willing to make an investment in a still less developed but rapidly improving new star kid on the mobile software development block? Then Flutter might be just right for you.
At the end of the day, it’s always a good choice to carefully evaluate your project specifics, priorities and roadmap for the future to compare the pros and cons of each framework.
Contact our mobile development experts for a consultation
WANT TO START A PROJECT?