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

# はじめに

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

[前回](https://qiita.com/midnightSuyama/items/87df15218b99e8ef6fb6)からの主な変更点は、App Store の予約、ガチャ排出率の開示、VPN 関連などです。

App Store の予約は以前「スーパーマリオラン」で実施されていましたが、先週から一般開発者向けにも開放されています。詳細は [Offering Your Apps for Pre-Order](https://developer.apple.com/app-store/pre-orders/) を参照。

ガチャ排出率の開示については、アイテム種類の定義次第ですが、この規約だけでは解釈が困難です。この辺りはアプリ申請時の審査員ガチャ次第なのかも。

VPN 関連は最近中国で VPN アプリを一斉削除した件もあり、専用の項目を設けたようです。ちなみに、先月からロシアでも VPN 禁止に。

修正項目内の 3.1.1 に関しては、2017年12月21日付の変更点ではありませんが、前回からの差分として掲載しました。

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

# 新規項目

## 2.3.11 App Store で予約を開始するアプリはその時点で動作する必要有。

> Apps you submit for pre-order on the App Store must be complete and deliverable as submitted. Ensure that the app you ultimately release is not materially different from what you advertise while the app is in a pre-order state. If you make material changes to the app (e.g. change business models), you should restart your pre-order sales.

## 3.1.1 ランダム性の課金アイテムは各種類の排出率を事前に開示。

> Apps offering “loot boxes” or other mechanisms that provide randomized virtual items for purchase must disclose the odds of receiving each type of item to customers prior to purchase.

## 3.2.1 Acceptable

### (Viii) 金融アプリは金融機関による公式の提供か API 使用が必要。

> Apps used for financial trading, investing, or money management should come from the financial institution performing such services or must use a public API offered by the institution in compliance with its Terms & Conditions.

## 5.4 VPN Apps

### VPN には NEVPNManager を使用。使用用途を明示。対象地域の法令を遵守。ライセンス情報は App Review Notes に記載。

> Apps offering VPN services must utilize the NEVPNManager API and must make a clear declaration of what user data will be collected and how it will be used. VPN apps must not violate local laws, and if you choose to make your VPN app available in a territory that requires a VPN license, you must provide your license information in the App Review Notes field.

# 修正項目

## 2.1 App Completeness

### 申請時には最終的なメタデータと URL 機能を完備。仮コンテンツ不可。要実機検証。ログイン機能にはデモアカウントを提供。アプリ内課金の状態不備は要説明。App Review をテスティングサービスとして扱うことは勘弁。不完全なバンドルや問題のあるバイナリは却下。

> Submissions to App Review, including apps you make available for pre-order, should be final versions with all necessary metadata and fully functional URLs included; placeholder text, empty websites, and other temporary content should be scrubbed before submission. Make sure your app has been tested on-device for bugs and stability before you submit it, and include demo account info (and turn on your back-end service!) if your app includes a login. If you offer in-app purchases in your app, make sure they are complete, up-to-date, and visible to the reviewer, or that you explain why not in your review notes. Please don’t treat App Review as a software testing service. We will reject incomplete app bundles and binaries that crash or exhibit obvious technical problems.

`including apps you make available for pre-order` を追記。

## 2.3.2 アプリ内課金を使うアプリは追加購入の必要性を明示。

> If your app includes in-app purchases, make sure your app description, screenshots, and previews clearly indicate whether any featured items, levels, subscriptions, etc. require additional purchases. If you decide to promote in-app purchases on the App Store, ensure that the in-app purchase Display Name, Screenshot and Description are appropriate for a public audience, that you follow the guidance found in Promoting Your In-App Purchases, and that your app properly handles the SKPaymentTransactionObserver method so that customers can seamlessly complete the purchase when your app launches.

`that you follow the guidance found in Promoting Your In-App Purchases` を追記。

## 2.5.1 パブリック API のみ使用。非推奨機能は段階的に廃止。API やフレームワークは本来の目的に使用。統合関係はアプリ説明欄に記載。

> Apps may only use public APIs and must run on the currently shipping OS. Learn more about public APIs. Keep your apps up-to-date and make sure you phase out any deprecated features, frameworks or technologies that will no longer be supported in future versions of an OS. Apps should use APIs and frameworks for their intended purposes and indicate that integration in their app description. For example, the HomeKit framework should provide home automation services; and HealthKit should be used for health and fitness purposes and integrate with the Health app.

`Apps should use APIs and frameworks for their intended purposes and indicate that integration in their app description. For example, the HomeKit framework should provide home automation services; and HealthKit should be used for health and fitness purposes and integrate with the Health app.` が旧 4.2.1 から移動。

## 3.1.1 In-App Purchase:

### ● 機能制限の解除には使用必須。アプリ内課金通貨によるチップが可能。アプリ内課金以外の課金導線は不可。

> If you want to unlock features or functionality within your app, (by way of example: subscriptions, in-game currencies, game levels, access to premium content, or unlocking a full version), you must use in-app purchase. Apps may use in-app purchase currencies to enable customers to “tip” digital content providers in the app. Apps and their metadata may not include buttons, external links, or other calls to action that direct customers to purchasing mechanisms other than in-app purchase.

`and their metadata` の記載を修正。

## 3.1.2(a) Permissible uses:

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

> You may offer a single subscription that is shared across your own apps and services, but these subscriptions may not extend to third party apps or services. Games offered in a game subscription must be owned or exclusively licensed by the developer (e.g. not part of a game publishing platform). Each game must be downloaded directly from the App Store, must be designed to avoid duplicate payment by a subscriber, and should not disadvantage non-subscriber customers.

`and services` `Games offered in a game subscription must be owned or exclusively licensed by the developer (e.g. not part of a game publishing platform). Each game must be downloaded directly from the App Store, must be designed to avoid duplicate payment by a subscriber, and should not disadvantage non-subscriber customers.` を追記。

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

> Subscriptions may include consumable credits, gems, in-game currencies, etc., and you may offer subscriptions that include access to discounted consumable goods (e.g. a platinum membership that exposes gem-packs for a reduced price).

`Subscriptions may not include consumable credits, gems, in-game currencies, etc., even when combined with other offerings, but` から `Subscriptions may include consumable credits, gems, in-game currencies, etc., and` に変更。

## 3.1.5 (a) Physical Goods and Services Outside of the App: 物品や外部サービスの支払いはアプリ内課金の適用外。

> If your app enables people to purchase goods or services that will be consumed outside of the app, you must use purchase methods other than in-app purchase to collect those payments, such as Apple Pay or traditional credit card entry.

`Apps may facilitate transmission of approved virtual currencies (e.g. Bitcoin, DogeCoin) provided that they do so in compliance with all state and federal laws for the territories in which the app functions.` が 3.1.5 (b) に移動。

## 3.1.5 (b) Cryptocurrencies: 仮想通貨の利用は対象地域の法令を遵守。

> Apps may facilitate transmission of approved virtual currencies (e.g. Bitcoin, DogeCoin) provided that they do so in compliance with all state and federal laws for the territories in which the app functions. Apps facilitating Initial Coin Offerings (“ICOs”), cryptocurrency futures trading, and other crypto-securities or quasi-securities trading must come from established banks, securities firms, futures commission merchants (“FCM”), or other approved financial institutions and must comply with all applicable law.

`Apps facilitating Initial Coin Offerings (“ICOs”), cryptocurrency futures trading, and other crypto-securities or quasi-securities trading must come from established banks, securities firms, futures commission merchants (“FCM”), or other approved financial institutions and must comply with all applicable law.` を追記。

## 3.2.2 Unacceptable

### (viii) バイナリーオプション取引の促進。ライセンスのない差金決済や為替など。

> Apps that facilitate binary options trading are not permitted on the App Store. Consider a web app instead. Apps that facilitate trading in contracts for difference (“CFDs”) or other derivatives (e.g. FOREX) must be properly licensed in all jurisdictions where the service is available.

`Apps that facilitate trading in contracts for difference (“CFDs”) or other derivatives (e.g. FOREX) must be properly licensed in all jurisdictions where the service is available.` を追記。

## 4.2.1 ARKit 対応アプリは優れた拡張現実体験が必要。

> Apps using ARKit should provide rich and integrated augmented reality experiences; merely dropping a model into an AR view or replaying animation is not enough.

`Apps should use APIs and frameworks for their intended purposes and indicate that integration in their app description. For example, the HomeKit framework should provide home automation services; and HealthKit should be used for health and fitness purposes and integrate with the Health app.` が 2.5.1 に移動。

## 4.2.6 商用のテンプレートや生成サービスによるアプリは却下。コンテンツ提供者による直提出は免除。

> Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app’s content. These services should not submit apps on behalf of their clients and should offer tools that let their clients create customized, innovative apps that provide unique customer experiences. Another acceptable option for template providers is to create a single binary to host all client content in an aggregated or “picker” model, for example as a restaurant finder app with separate customized entries or pages for each client restaurant, or as an event app with separate entries for each client event.

`unless they are submitted directly by the provider of the app’s content. These services should not submit apps on behalf of their clients and should offer tools that let their clients create customized, innovative apps that provide unique customer experiences. Another acceptable option for template providers is to create a single binary to host all client content in an aggregated or “picker” model, for example as a restaurant finder app with separate customized entries or pages for each client restaurant, or as an event app with separate entries for each client event.` を追記。

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

`Provide Number and Decimal keyboard types as described in the App Extension Programming Guide;` の項目が消滅。

App Extension 開始時から存在していた項目なので、真に数字キーボードが不要になったのか、単に明記を削っただけなのか微妙。

## 4.7 HTML5 Games, Bots, etc.

### ストア形式でなければ他者提供のコードを実行可能。ソフトウェアは (1) 無料かアプリ内課金、(2) WebKit 内の機能限定、(3) Apple Developer Program の開発者提供、(4) App Review Guidelines を遵守。

> Apps may contain or run code that is not embedded in the binary (e.g. HTML5-based games, bots, etc.), as long as code distribution isn’t the main purpose of the app, the code is not offered in a store or store-like interface, and provided that the software (1) is free or purchased using in-app purchase; (2) only uses capabilities available in a standard WebKit view; your app must use WebKit and JavaScript Core to run third party software and should not attempt to extend or expose native platform APIs to third party software; (3) is offered by developers that have joined the Apple Developer Program and signed the Apple Developer Program License Agreement; and (4) adheres to the terms of these App Review Guidelines (e.g. does not include objectionable content). You must provide an index of software and metadata available in your app upon request.

`uses in-app purchase to unlock features and functionality` が消滅。