In this article, we visualise the current state of things for the more popular iOS and Android cross-platform frameworks. Read on to see a definitive answer on what each framework can and cannot do, and how they compare.
Choosing a cross-platform SDK because it is supposed to increase speed or decrease costs is very likely to be a bad idea. What you should aim to get out of a cross-platform team is value for your users and, by extension, to your business. To obtain value, you need to be aware of your teams' processes and state of mind, and still be aware of what kind of value a framework can bring, and in which conditions.
Here we are presenting one way to help inform your decision making when attempting to create or pivot, a mobile product. It is in no way a holy grail or one size fits all answer. For further background information or if you want to find out more details, check out some of our other posts for a more in-depth discussion on the issue of cross-platform frameworks:
We decided to make this cross-platform choice diagram to try and explain the thought process that should happen with this decision point. It's not a process to do on a whim and we hope the diagram sheds light on potential areas you may not have considered in your deliberations.
The diagram is free to download, print, share and use — the diagram is licensed under the Creative Commons Attribution-ShareAlike 4.0 International licence. Just don’t take out the Novoda logo, basically, and you’ll be alright. We hope it'll spark discussions and help you have an informed choice. We’ve highlighted some areas of interest that we think may be useful when looking into cross-platform frameworks like Xamarin, Flutter and React Native.
Choosing a solution for your mobile products is a complex task. Involving the evaluation of cross-platform frameworks means considering a lot of tools and a lot of potential programming languages, ecosystems and talent pools. What you should aim to get out of a cross-platform team is value for your users and therefore value for your business. To obtain value, you need to be aware of your teams' processes and state of mind, and still be aware of what kind of value a framework can bring, and in which conditions. We hope this diagram helps you towards that goal.