App Quick pass Apple AppStore review nine tips

"IT168 Technology" is probably the most frustrating thing for mobile app developers to do with their hard-to-develop apps, failure to pass an Apple AppStore audit, or encounter a rack when applying updates. Apple's AppStore review process and standards have always been opaque and have been very cumbersome to complain about. VentureBeat's columnist, the founder and CEO of Xamarin, Nat Friedman, based on the experience of the 220,000 developers of the Xamarin Mobile development Framework, summarizes 9 reasons why apps are being appstore by Apple. Compile for your reference:

　　

First, use "Beta" or other names that might make Apple think your app hasn't been developed yet.

As many of Google's products are released "Beta", there is a trend in the IT industry to name the final product plus a "beta". And Apple is very strict about it. Any product with a similar word will be considered unfinished. We've seen a lot of products like "beta", "Preview" or "version 0.9" failed to pass AppStore audit

Second, the loading time is too long

All mobile operating systems (IOS, Android, even windows) are limited to the maximum load time of the app. For iOS, it's about 15 seconds, and if your app fails to start in 15 seconds, the OS will kill the process.

Even if your app starts during this time, the network connection speed, hardware, and other environments can also cause your app to load too long during the audit. Therefore, do not rely solely on the iOS simulator, must be in real network and real hardware environment testing, and it is best to keep some old phone to ensure that all users can experience relatively fast loading speed.

Third, linking to third-party payment systems

Apple requires all the digital content to be done through itunes's built-in in-app purchases. Including one-time purchase or registration fee. If your app offers other ways to buy, your app will definitely get off the rack. That's why the Kindle app doesn't allow users to buy new books directly from the app.

It's not even possible for apps to provide third-party payment links through the web. The Dropbox app was rejected by Apple as an example. Dropbox's app provides a link to buy more storage space on the login screen and fails the apple audit. This is not only an impact on Dropbox apps, it's even for all apps that use the Dropbox API.

Therefore, be sure to check your application development process to ensure that all digital content purchases are done through the user's itunes account. Note that Apple only makes this restriction on digital content, which is why some travel apps can book hotels and tickets through the app.

Four, don't mention support for other platforms

Not just apples. No market wants you to mention a competitor's name. So if your app is already running on Android or Windows, say it on your own website and don't mention it in the app's description.

　Five, some of the problems of localization

Your app users may come from all over the world, and even if you don't have a multi-lingual version, writing the yen symbol as a euro when in-app purchases is a sign that you're an immature developer.

Therefore, use components like asnsnumberformatter or invariant culture and emulators to test the user experience in different regions, ensuring that formats such as dates conform to the user's local format requirements.

We have seen the application of a European application developer, because the Apple AppStore refused to properly handle the negative latitude and longitude (note: The longitude of Apple headquarters is-122.03). Therefore, be sure to check your application for any latitude and longitude on the map to run. Special attention should be paid to the change of positive and negative longitude through the Prime Meridian and positive and negative latitude.

　　VI, improper use of storage and file systems

After the launch of the iOS5.1, Apple had an upgrade of the app because the developer backed up a 2MB-size database from the app to the filesystem, violating icloud's rules for backing up only user-generated content.

There is no need to back up any so-called "renewable data" that is static or is either applied to it or is easily downloaded from a remote server. For non-user data, you can select a cache location or select the Do not require backup property.

　VII, crashes when a user denies a permission request

At IOS6, users must elevate their permission requests to applications that attempt to access address books, photo sets, geolocation, calendars, reminders, Bluetooth, Twitter and Facebook accounts. If the user rejects the app's permission request, Apple requires the app to continue working.

This is automatically tested at the time of audit and is automatically rejected if it does not work correctly. Therefore, be sure to carefully test all the "Allow" and "deny" combinations when the app uses the data, and also include situations where the user starts allowing permission and then rejects it.

　　The incorrect use of icons and buttons

Many iOS apps are rejected not because of performance or functionality, just because of some small UI problems. Developers want to make sure the app is consistent in appearance and functionality when using the built-in Apple icons and buttons. Uibuttonbarsystemitem can be used for testing. Also, be familiar with Apple's "human-Computer Interaction Guide"

For example, in addition to creating new content, you can't use Apple's "Compose" icon to represent any other use. Apple's engineers want the app's behavior to be as predictable as possible. The use of built-in icons and buttons is therefore particularly stringent.

　　Ninth, incorrect use of trademarks and logos

Do not use someone else's logo or Apple icon on your app's image. Also do not use an icon with an iphone pattern. We have seen examples in which the trademark is rejected in the keyword.

On the other hand, your app also needs to make explicit attribute information (such as Google Maps or Nokia maps) in the built-in map, otherwise it will be rejected.

Of course, if your app is rejected or down, don't worry, just find the problem and submit it again. In addition, Apple provides an emergency audit mechanism for critical bugs or security fixes. However, if developers overuse the emergency audit mechanism, they may be banned from use in the future.

Of course, it is best to try to pass the audit once. So, of course, the developer carefully reads Apple's submission guide and provides high-quality apps.

Finally, let's add one more: Beware of "yellow" images.

App Quick pass Apple AppStore review nine tips