Return to Answer

The big problem with hybrid apps is the fragmentation of the frameworks: there are clearly much more of them (Ionic, Xamarin, React Native, etc) than there are native mobile platforms of interest (usually just two, Android and iOS). These frameworks compete, emerge, decline, so going hybrid will not save you from jumping from platform to platform even if you plan to keep your current team for life.

Google and Apple are trying they best in providing and supporting editors, debuggers, testing frameworks, refactoring tools and other means to develop for they platforms. Hence I would take a typical wording "it is just much easier to develop a hybrid app, edit with your favourite editor and open in a browser" with the reasonable reservation. Xamarin and React Native are development platforms, same as Swift or Java/Android are, and while "hello world" may look shorter, eventually should take the comparable time to learn properly.

If, for any case, a need for native components would arise (for instance, existing third party library must be integrated), you will end up with three frameworks rather than two: iOS, Android and your hybrid framework on the top, ending up with more complex architecture. Debugging such apps, stepping between cross-layer calls, logging all layers, keeping code in sync is complex to at times impossible.

Some say the "app will look exactly the same for all platforms". Is it really a good thing? Android app must look like Android app and iOS app must look like iOS app.

What about the new features? Wearables? Instant apps now offered by Android platform? Hybrid apps now support many native features, but do they really support all of them? At any time, immediately?

Finally, not just performance and user experience, but also security may be more on the side of the native app. Hybrid framework adds the layer of indirection that may have own bugs, security bugs including.

Concluding all above, under the possibility to choose, I would definitely either go for the two native apps, one for iOS, and one for Android or alternatively would simply design a mobile version of the website without bothering with app development for any platform at all.

The big problem with hybrid apps is the fragmentation of the frameworks: there are clearly much more of them (Ionic, Xamarin, React Native, etc) than there are native mobile platforms of interest (usually just two, Android and iOS). These frameworks compete, emerge, decline, so going hybrid will not save you from jumping from platform to platform even if you plan to keep your current team for life.

Google and Apple are trying they best in providing and supporting editors, debuggers, testing frameworks, refactoring tools and other means to develop for they platforms. Hence I would take a typical wording "it is just much easier to develop a hybrid app, edit with your favourite editor and open in a browser" with the reasonable reservation. Xamarin and React Native are development platforms, same as Swift or Java/Android are, and while "hello world" may look shorter, eventually should take the comparable time to learn properly.

If, for any case, a need for native components would arise (for instance, existing third party library must be integrated), you will end up with three frameworks rather than two: iOS, Android and your hybrid framework on the top, ending up with more complex architecture. Debugging such apps, stepping between cross-layer calls, logging all layers, keeping code in sync is complex to at times impossible.

Some say the "app will look exactly the same for all platforms". Is it really a good thing? Android app must look like Android app and iOS app must look like iOS app.

What about the new features? Wearables? Instant apps now offered by Android platform? Showing additional data on external display? Hybrid apps now support many native features, but do they really support all of them? At any time, immediately?

Finally, not just performance and user experience, but also security may be more on the side of the native app. Hybrid framework adds the layer of indirection that may have own bugs, security bugs including.

Concluding all above, under the possibility to choose, I would definitely either go for the two native apps, one for iOS, and one for Android or alternatively would simply design a mobile version of the website without bothering with app development for any platform at all.

The big problem with hybrid apps is the fragmentation of the frameworks: there are clearly much more of them (Ionic, Xamarin, React Native, etc) than there are native mobile platforms of interest (usually just two, Android and iOS). These frameworks compete, emerge, decline, so going hybrid will not save you from jumping from platform to platform even if you plan to keep your current team for life.

Google and Apple are trying they best in providing and supporting editors, debuggers, testing frameworks, refactoring tools and other means to develop for they platforms. Hence I would take a typical wording "it is just much easier to develop a hybrid app, edit with your favourite editor and open in a browser" with the reasonable reservation. Xamarin and React Native are development platforms, same as Swift or Java/Android are, and while "hello world" may look shorter, eventually should take the comparable time to learn properly.

If, for any case, a need for native components would arise (for instance, existing third party library must be integrated), you will end up with three frameworks rather than two: iOS, Android and your hybrid framework on the top, ending up with more complex architecture. Debugging such apps, stepping between cross-layer calls, logging all layers, keeping code in sync is complex to at times impossible.

Some say the "app will look exactly the same for all platforms". Is it really a good thing? Android app must look like Android app and iOS app must look like iOS app.

What about the new features? Wearables? Instant apps now offered by Android platform? Hybrid apps now support many native features, but do they really support all of them? At any time, immediately?

Finally, not just performance and user experience, but also security may be more on the side of the native app. They add the layer of indirection that may have own bugs, security bugs including.

Concluding all above, under the possibility to choose, I would definitely either go for the two native apps, one for iOS, and one for Android or alternatively would simply design a mobile version of the website without bothering with app development for any platform at all.

The big problem with hybrid apps is the fragmentation of the frameworks: there are clearly much more of them (Ionic, Xamarin, React Native, etc) than there are native mobile platforms of interest (usually just two, Android and iOS). These frameworks compete, emerge, decline, so going hybrid will not save you from jumping from platform to platform even if you plan to keep your current team for life.

Google and Apple are trying they best in providing and supporting editors, debuggers, testing frameworks, refactoring tools and other means to develop for they platforms. Hence I would take a typical wording "it is just much easier to develop a hybrid app, edit with your favourite editor and open in a browser" with the reasonable reservation. Xamarin and React Native are development platforms, same as Swift or Java/Android are, and while "hello world" may look shorter, eventually should take the comparable time to learn properly.

If, for any case, a need for native components would arise (for instance, existing third party library must be integrated), you will end up with three frameworks rather than two: iOS, Android and your hybrid framework on the top, ending up with more complex architecture. Debugging such apps, stepping between cross-layer calls, logging all layers, keeping code in sync is complex to at times impossible.

Some say the "app will look exactly the same for all platforms". Is it really a good thing? Android app must look like Android app and iOS app must look like iOS app.

What about the new features? Wearables? Instant apps now offered by Android platform? Hybrid apps now support many native features, but do they really support all of them? At any time, immediately?

Finally, not just performance and user experience, but also security may be more on the side of the native app. Hybrid framework adds the layer of indirection that may have own bugs, security bugs including.

Concluding all above, under the possibility to choose, I would definitely either go for the two native apps, one for iOS, and one for Android or alternatively would simply design a mobile version of the website without bothering with app development for any platform at all.

The big problem with hybrid apps is the fragmentation of the frameworks: there are clearly much more of them (Ionic, Xamarin, React Native, etc) than there are native mobile platforms of interest (usually just two, Android and iOS). These frameworks compete, emerge, decline, so going hybrid will not save you from jumping from platform to platform even if you plan to keep your current team for life.

Google and Apple are trying they best in providing and supporting editors, debuggers, testing frameworks, refactoring tools and other means to develop for they platforms. Hence I would take a typical wording "it is just much easier to develop a hybrid app, edit with your favourite editor and open in a browser" with the reasonable reservation. Xamarin and React Native are development platforms, same as Swift or Java/Android are, and while "hello world" may look shorter, eventually should take the comparable time to learn properly.

If, for any case, a need for native components would arise (for instance, existing third party library must be integrated), you will end up with three frameworks rather than two: iOS, Android and your hybrid framework on the top, ending up with more complex architecture. Debugging such apps, stepping between cross-layer calls, logging all layers, keeping code in sync is complex to at times impossible.

Some say the "app will look exactly the same for all platforms". Is it really a good thing? Android app must look like Android app and iOS app must look like iOS app.

What about the new features? Wearables? Instant apps now offered by Android platform? Hybrid apps now support many native features, but do they really support all of them? At any time, immediately?

Finally, not just performance and user experience, but also security may be more on the side of the native app. They add the layer of indirection that may have own bugs, security bugs including.

Concluding all above, under the possibility to choose, I would definitely go for the two native apps, one for iOS, and one for Android. Unfortunately, it is not so that you are always the person making the decision, and due this it is useful to know one or another hybrid framework as well.

The big problem with hybrid apps is the fragmentation of the frameworks: there are clearly much more of them (Ionic, Xamarin, React Native, etc) than there are native mobile platforms of interest (usually just two, Android and iOS). These frameworks compete, emerge, decline, so going hybrid will not save you from jumping from platform to platform even if you plan to keep your current team for life.

Google and Apple are trying they best in providing and supporting editors, debuggers, testing frameworks, refactoring tools and other means to develop for they platforms. Hence I would take a typical wording "it is just much easier to develop a hybrid app, edit with your favourite editor and open in a browser" with the reasonable reservation. Xamarin and React Native are development platforms, same as Swift or Java/Android are, and while "hello world" may look shorter, eventually should take the comparable time to learn properly.

If, for any case, a need for native components would arise (for instance, existing third party library must be integrated), you will end up with three frameworks rather than two: iOS, Android and your hybrid framework on the top, ending up with more complex architecture. Debugging such apps, stepping between cross-layer calls, logging all layers, keeping code in sync is complex to at times impossible.

Some say the "app will look exactly the same for all platforms". Is it really a good thing? Android app must look like Android app and iOS app must look like iOS app.

What about the new features? Wearables? Instant apps now offered by Android platform? Hybrid apps now support many native features, but do they really support all of them? At any time, immediately?

Finally, not just performance and user experience, but also security may be more on the side of the native app. They add the layer of indirection that may have own bugs, security bugs including.

Concluding all above, under the possibility to choose, I would definitely either go for the two native apps, one for iOS, and one for Android or alternatively would simply design a mobile version of the website without bothering with app development for any platform at all.