DEV Community

Discussion on: What is the Future of Mobile App Development in Hybrid Apps?

Collapse
 
lilithkarapetyan profile image
Lilit Karapetyan

I have to disagree with the following sentence "If they notice it's a hybrid app, there's a good possibility it won't be accepted into the App Store.". As you might know, the result of an app built by Xcode is just a regular .ipa file. You upload a standard IOS app file to the App Store. As far as I know, Apple has no official announcement about not supporting hybrid apps. Let's take a closer look to understand why we can still freely publish our hybrid apps to App Store and Play market.
We can divide the hybrid apps into two main categories: the ones using a WebView and the ones which map their components to the corresponding native ones. For the first case, WebView is just a regular native component, which is basically a browser inside the app; since WebView is native component, the Apple team can't ban its usage; therefore, they can't ban the Hybrid apps using the WebView. For the second case, after building the app for production, all the non-native elements are being mapped to the corresponding ones for that specific platform. This means that after building the app, we get a regular app using native components. Again, Apple can't ban apps using these apps because they are using the technology Apple accepts.
If you had such an experience when the App Store team did not accept your app, are you sure that the reason was the hybrid technology you used?

Collapse
 
aleksanderlubych profile image
Aleksander Lubych

Amen to that.

Usually the problem with not accepting the app is not that its hybrid, but because it has bad UX/UI in general. I think we will have mostly hybrid apps in future TBH, there is no need to spend that much money to build things 3 times (web, iOS, Android), if you can build once and use it everywhere.