Apple vs HTML – is it time to go native?!

Using a cross-platform technology to cover all currently available mobile platforms always saved the development time and efforts. You could create a responsive HTML app that will nicely run in your desktop and mobile browser, as well as you can wrap it as a mobile app and load into a mobile store.

However, not long ago Apple has started to activelly reject such HTML mobile apps following the recent App Store Review Guidelines, assuming that:

  1. The app is more of a web page then a mobile application
  2. Your app is too slow or unresponsive
  3. It does not handle online and offline states
  4. Your app does not property scale to the resolution
  5. You are using workarounds breaking the rules

So what can be done about that🤷‍♂️? Can you slightly change your HTML app to be compliant with all above? Or you would need to completely rewrite your app into a native?

Well, you can definitely consider adjusting the design, improve the app behaviour, introduce integration with the mobile features, increase the performance and such with the use of HTML5 mobile framework. But, will it be a ⏳permanent solution?

From our experience – unfortunately, it will not! The sooner you’ll implement everything native the better. This will not only simplify the compliance process but will also improve the performance, stability and supportability of your application. And also exclude or at least minimize the headache of dealing with new rules and routines.

The good thing is that you will only have to replace the web part as the whole server-side, the logic and integrations could remain the same.

If you had a web logic in your server code – appropriate changes will be required there as well☝️.

Need help in porting your HTML app into iOS? Just let us know!