[martechads]

Please see the message below. This is the response I received from apple about my app built with MobiOne. I know many people using MobiOne have had their apps accepted by Apple. What do I need to change about my setup or building that they say needs to be native?

We found the user interface of your app is not of sufficient quality to be appropriate for the App Store. Apps that provide a poor user experience are not in compliance with the App Store Review Guidelines.

Specifically, we have found that your app does not take advantage of the iOS platform. It would be appropriate to add iOS specific UI and user functionality rather than displaying just text and table views.

Please evaluate whether you can make the necessary revisions to improve the user experience of your app.

Alternatively, you may wish to consider building a web app using HTML5. HTML5 is the major new version of HTML and enables audio and video to play natively in the browser without requiring proprietary plug-ins. Using HTML5, web apps look and behave like native iPhone and iPad apps, and using HTML5’s Offline Application Cache, your web apps work even when the device is offline. With web apps, you have flexibility to deliver as much or as little functionality as you desire.

If you wish to build an HTML5 web app, you can do so and distribute it directly from your web site. It is not appropriate to submit an HTML5 web app to the App Store.

To get started with iPhone or iPad web apps, please review Getting Started with iPhone Web Apps.

For a description of the HTML elements and attributes you can use in Safari on iPhone, check out Safari HTML Reference: Introduction.

[support-michael]

@martechads

This is a standard response from Apple app reviewers when they deem the UX below a basic usability level. They usually care less about the webapp nature of the app than they do the user experience. For example if the app uses low quality images or poor UI layout, this will get your app banned in a heart beat. Other considerations are general screen organization and feature distribution and access. For example a zillion buttons on a screen or a really long menu are other examples I’ve seen caused app rejection. Then finally it could be that your app truly does not provide value beyond a traditional webapp; but it usually something else. Feel free to post screenshots for community review and suggestions.

[Paul G]

Hello,

Can someone explain why you would want to use Mobione to create a native IOS app instead of a web app?

Other than having Apple list your native app in Itunes, how is a Mobione created native app different from a Mobione created web app?

Paul

[support-michael]

@Paul G

Great question. In addition to creating mobile webapps, MobiOne produces hybrid native apps. The hybrid app runs a packaged version of your webapp in an embedded browser of the native executable. Where the hybrid app differs is that your webapp can access native services via a JavaScript api on the device that are not available to your webapp in the std browser. MobiOne uses the OSS Cordova/PhoneGap framework for its native apps. We have not really started advertising it yet but you can access services such as the camera. See this api listing http://docs.phonegap.com/en/1.1.0/index.html

Other reasons are as you mentioned, apps have such a strong mindshare over webapps. So app store access and installation are common user expectations.

[Author]

Posts