22 May 2019
Mostly on social media I advise against building hybrid apps. I have used ionic, react native (RN), and Xamarin in my mobile app career. I feel that it is really bad to advise against something without explaining the why. I’m going to explain why I advise against hybrid development, but also when to use it and which platform I recommend.
What is a hybrid app?
A hybrid app is an app made for multiple mobile platforms (iOS, Android, Windows) using one coding language. Examples of these frameworks are ionic, react native, Xamarin, and flutter.
Why use a hybrid framework?
My personal choice
I originally learned to develop natively. From learning
Objective-C at NASA to jumping into Android security in
Java. Given that background, I almost always try to go native, BUT my hybrid framework of choice is RN. I like react native because it was easy for me to learn after spending a lot of time with
nodeJS, but also because it’s fairly easy to port your code from RN to native code.
All that being said, hybrid is a short term solution. You would build a hybrid app for say an mvp (minimal viable product) but as your audience and your feature list grows, you should really move to native Android and iOS. Not moving from hybrid at this point could affect key user features such as load time, or even memory. You might also be limiting yourself of features readily available in the native platform.
Still want to know if a hybrid app is right for your idea? Setup a call with meBy: Keheira If you would like to donate to keep the content coming or just as a thank you, you can buy me a coffee or use cashapp.
tags: android - iOS - Windows - hybrid apps - react native - ionic - Xamarin - flutter - advice