新 App Store 審査ガイドライン 翻訳&差分ガイド 2016年9月号

# はじめに

これは2016年9月1日付けで変更された App Store 審査ガイドラインの翻訳&差分ガイドです。

[前回](http://qiita.com/midnightSuyama/items/54d65502b15d9ca07a19)の全面改訂版からの主な変更点は、予告されていたサブスクリプションの仕様変更、iOS 10 配信にともなう SiriKit / Stickers 項目の追加、そして [App Store Improvements](https://developer.apple.com/support/app-store-improvements/) の反映になります。

2.4.1 と 2.5.1 に関しては、6月改訂の翌月に静かに修正されているので、正確には2016年9月1日付けの変更点ではありませんが、6月改訂からの差分として掲載しました。

[https://developer.apple.com/app-store/review/guidelines/](https://developer.apple.com/app-store/review/guidelines/)

# 新規項目

## 2.5.11 SiriKit

### (i) SiriKit を利用するアプリは追加アプリ不要なインテントのみ使用。

> Apps integrating SiriKit should only sign up for intents they can handle without the support of an additional app and that users would expect from the stated functionality. For example, if your app is a meal planning app, you should not incorporate an intent to start a workout, even if the app shares integration with a fitness app.

### (ii) plist 定義の語彙やフレーズと SiriKit 機能の関係を要確認。

> Ensure that the vocabulary and phrases in your plist pertains to your app and the SiriKit functionality of the intents the app has registered for.

### (iii) Siri とのやりとりに広告の挿入は不可。タスク完了に必要な場合のみ UI を提供。

> Resolve the Siri request in the most direct way possible and do not insert ads or other marketing between the request and its fulfillment. Only present interstitial UI when required to complete the task (e.g. asking the user to specify a particular type of workout).

## 3.2.2 Unacceptable

### (vi) 使用条件の付加。レビューや他アプリのダウンロードの強要。

> Apps should allow a user to get what they’ve paid for without performing additional tasks, such as posting on social media, uploading contacts, checking in to the app a certain number of times, etc. Apps should not force users to rate the app, review the app, download other apps, or take other similar actions in order to access functionality, content, or use of the app.

## 4.4.3 Stickers

### ステッカー拡張機能もステッカーパックも不快なコンテンツは不可。

> Stickers are a great way to make Messages more dynamic and fun, letting people express themselves in clever, funny, meaningful ways. Whether your app contains a sticker extension or you’re creating free-standing sticker packs, its content shouldn’t offend users, create a negative experience, or violate the law.

### (i) ステッカーは App Store に適応する必要有。

> In general, if it wouldn’t be suitable for the App Store, it doesn’t belong in a sticker.

### (ii) 対象地域の法令を遵守。

> Consider regional sensitivities, and do not make your sticker pack available in a country where it could be poorly received or violate local law.

### (iii) 理解しづらいステッカーは要説明。

> If we don’t understand what your stickers mean, include a clear explanation in your review notes to avoid any delays in the review process.

### (iv) 内輪向けのステッカーは不可。

> Ensure your stickers have relevance beyond your friends and family; they should not be specific to personal events, groups, or relationships.

### (v) コンテンツには著作権・商標権・パブリシティ権が必要。要請に応じて検証用書類を提出。使用権のないコンテンツを含むアプリは削除。再犯者は開発者登録を抹消。

> You must have all the necessary copyright, trademark, publicity rights, and permissions for the content in your stickers, and shouldn’t submit anything unless you’re authorized to do so. Keep in mind that you must be able to provide verifiable documentation upon request. Apps with sticker content you don’t have rights to use will be removed from the App Store and repeat offenders will be removed from the Developer Program. If you believe your content has been infringed by another provider, submit a claim here.

## 5.1.1 Data Collection and Storage

### (iv) SafariViewContoller の表示を隠すことや事前同意のない追跡は不可。

> SafariViewContoller must be used to visibly present information to users; the controller may not be hidden or obscured by other views or layers. Additionally, an app may not use SafariViewController to track users without their knowledge and consent.

# 修正項目

## 2.3.4 プレビューはアプリ画面のキャプチャ限定。ナレーションやキャプションの追加は可能。

> Previews are a great way for customers to see what your app looks like and what it does. To ensure people understand what they’ll be getting with your app, previews may only use video screen captures of the app itself. Stickers and iMessage extensions may show the user experience in the Messages app. You can add narration and video or textual overlays to help explain anything that isn’t clear from the video alone.

`Stickers and iMessage extensions may show the user experience in the Messages app.` を追記。

Stickers と iMessage 拡張機能はメッセージアプリの画面で紹介。

## 2.3.7 ユニークなアプリ名と正確なキーワードを指定。アプリ名は 50 文字まで。名前以外の記述を含めることは不可。不適切なキーワードは Apple により変更。

> Choose a unique app name, assign keywords that accurately describe your app, and don’t try to pack any of your metadata with trademarked terms, popular app names, or other irrelevant phrases just to game the system. App names must be limited to 50 characters and should not include terms or descriptions that are not the name of the app. Apple may modify inappropriate keywords at any time.

`App names must be limited to 50 characters and should not include terms or descriptions that are not the name of the app.` を追記。

SEO を意図した説明的な名称は禁止。

## 2.4.1 iPhone アプリは iPad でも動作。ユニバーサルアプリ推奨。

> To ensure people get the most out of your app, iPhone apps should run on iPad whenever possible. We encourage you to consider building universal apps so customers can use them on all of their devices. Learn more about Universal apps.

`Learn more about Universal apps.` を追記。

## 2.5.1 パブリック API のみ使用。

> Apps may only use public APIs. Learn more about public APIs.

`Learn more about public APIs.` を追記。

## 3.1.1 In-App Purchase:

> Remember to assign the correct purchasability type or your app will be rejected.

箇条形式に変更。文頭の `Please` が消滅。

## 3.1.2 Subscriptions: App Store のカテゴリにかかわらず自動更新が適用可能。自動更新を含む場合は以下遵守。

> Apps may offer auto-renewing in-app purchase subscriptions, regardless of category on the App Store. When incorporating auto-renewable subscriptions into your app, be sure to follow the guidelines below.

限定的だった自動更新の対象は `regardless of category` に変更。

## 3.1.2(a) Permissible uses: 自動更新には継続的な価値が必要。(適例： 新しいゲームレベル、エピソードコンテンツ、マルチプレイヤー対応、重要なアップデート、メディアコンテンツの更新、SaaS、クラウド対応) 追加事項：

> If you offer an auto-renewing subscription, you must provide ongoing value to the customer. While the following list is not exhaustive, examples of appropriate subscriptions include: new game levels; episodic content; multi-player support; apps that offer consistent, substantive updates; access to large collections of, or continually updated, media content; software as a service (“SAAS”); and cloud support. In addition:

### ● サブスクリプションは単品売りと並べて提供可能。

> Subscriptions may be offered alongside a la carte offerings (e.g. you may offer a subscription to an entire library of films as well the purchase or rental of a single movie).

### ● サブスクリプションは自身のアプリ間で共有可能。他者共有は不可。ユーザのすべてのデバイスで利用できる必要有。

> You may offer a single subscription that is shared across your own apps, but these subscriptions may not extend to third party apps or services. Subscriptions must work on all of the user’s devices where the app is available. Learn more about sharing a subscription across your apps.

### ● レビューや他アプリのダウンロードの強要は不可。

> Apps must not force users to rate the app, review the app, download other apps, or other similar actions in order to access functionality, content, or use of the app.

### ● 使用条件の付加は不可。

> As with all apps, those offering subscriptions should allow a user to get what they’ve paid for without performing additional tasks, such as posting on social media, uploading contacts, checking in to the app a certain number of times, etc.

### ● サブスクリプションには消耗品を含めないことも割引で含めることも可能。

> Subscriptions may not include consumable credits, gems, in-game currencies, etc., even when combined with other offerings, but you may offer subscriptions that include access to discounted consumable goods (e.g. a platinum membership that exposes gem-packs for a reduced price).

### ● 既存アプリをサブスクリプションベースに変更する場合は既存ユーザが購入した機能を補填。

> If you are changing your existing app to a subscription-based business model, you should not take away the primary functionality existing users have already paid for. For example, let customers who have already purchased a “full game unlock” continue to access the full game after you introduce a subscription model for new customers.

## 3.1.2(b) Upgrades and Downgrades: シームレスかつ課金内容の重複を避ける制御が必要。

> Users should have a seamless upgrade/downgrade experience and should not be able to inadvertently subscribe to multiple variations of the same thing. Review best practices on managing your subscription upgrade and downgrade options.

## 3.1.2(c) Subscription Information: 登録前に課金内容を明示。「契約／税金／口座情報」の契約別紙 2 の要件を伝えているか要確認。

> Before asking a customer to subscribe, you should clearly describe what the user will get for the price. How many issues per month? How much cloud storage? What kind of access to your service? Also ensure you clearly communicate the requirements described in Schedule 2 of your agreement in Agreements, Tax, and Banking.

## 3.1.3 Content-based “Reader” Apps: 課金導線がなければ購入済みコンテンツの利用は可能。

> Apps may allow a user to access previously purchased content or content subscriptions (specifically: magazines, newspapers, books, audio, music, video, access to professional databases, VoIP, cloud storage, and approved services such as educational apps that manage student grades and schedules), provided the app does not direct users to a purchasing mechanism other than IAP.

`subscriptions` から `content subscriptions` に変更。

## 4. Design

### シンプルで洗練され革新的かつ使いやすい製品を要望。以下最低基準。承認後も動作しない・劣化したアプリは削除。

> Apple customers place a high value on products that are simple, refined, innovative, and easy to use, and that’s what we want to see on the App Store. Coming up with a great design is up to you, but the following are minimum standards for approval to the App Store. And remember that even after your app has been approved, you should update your app to ensure it remains functional and engaging to new and existing customers. Apps that stop working or offer a degraded experience may be removed from the App Store at any time.

`And remember that even after your app has been approved, you should update your app to ensure it remains functional and engaging to new and existing customers. Apps that stop working or offer a degraded experience may be removed from the App Store at any time.` を追記。

削除対応は2016年9月7日から実施。修正猶予は30日間。

## 4.4 Extensions

### App Extension Programming Guide を遵守。ヘルプ画面と設定インターフェースを含める必要有。拡張機能は説明に明記。

> Apps hosting or containing extensions must comply with the App Extension Programming Guide or the Safari Extensions Development Guide and should include some functionality, such as help screens and settings interfaces where possible. You should clearly and accurately disclose what extensions are made available in the app’s marketing text.

`Extension views should not include marketing, advertising, or in-app purchases.` が 4.4.1 に移動。

`You should clearly and accurately disclose what extensions are made available in the app’s marketing text.` を追記。

## 4.4.1 キーボード拡張機能の追加規則。

`Have a primary category of Utilities when the keyboard is the main point of the app; and` が消滅。

以下、`They must not` 項目を追記。

### ● 宣伝やアプリ内課金を含める

> Include marketing, advertising, or in-app purchases;

### ● 設定アプリを除く他アプリの起動

> Launch other apps besides Settings; or

### ● キー動作の変更

> Repurpose keyboard buttons for other behaviors (e.g. holding down the “return” key to launch the camera.

## 5.1.1 Data Collection and Storage

### (i) ユーザデータの収集にはプライバシーポリシーと同意が必要。

> Apps that collect user or usage data must have a privacy policy and secure user consent for the collection. This includes—but isn’t limited to—apps that implement HealthKit or other health/medical technologies, HomeKit, Keyboard extensions, Apple Pay, Stickers and iMessage extensions, include a login, or access user data from the device (e.g. location, contacts, calendar, etc.).

`user data` から `user or usage data` に変更。`Stickers and iMessage extensions` を追記。

### (ii) 主機能や法的に必要性がない個人情報の要求は不可。主機能が対象の SNS と無関係の場合はログイン以外の仕組みが必要。プロフィールの取得や共有・招待は主機能枠外。

> If your app doesn’t include significant account-based features, let people use it without a log-in. Apps may not require users to enter personal information to function, except when directly relevant to the core functionality of the app or required by law. If your core app functionality is not related to a specific social network (e.g. Facebook, WeChat, Weibo, Twitter, etc.), you must provide access without a login or via another mechanism. Pulling basic profile information, sharing to the social network, or inviting friends to use the app are not considered core app functionality.

`If your core app functionality is not related to a specific social network (e.g. Facebook, WeChat, Weibo, Twitter, etc.), you must provide access without a login or via another mechanism. Pulling basic profile information, sharing to the social network, or inviting friends to use the app are not considered core app functionality.` を追記。