WWDC Quick Look 💓 By SwiftGGTeam
中文 EN 日本語
What's new in App Store Connect

What's new in App Store Connect

App Store ConnectApp ClipsGame CenterIn-App PurchaseApp Store Connect API
Watch original video

Highlight

App Store Connect added App Clip testing and card configuration, Game Center challenges and cycle rankings, in-app purchase family sharing, and more than 200 App Store Connect API endpoints in 2020, allowing release, testing, and operation configuration to be completed in the same set of background processes.

Core Content

Publishing an app has long been more than just uploading binary files. A team may need to prepare the entrance URL of the App Clip at the same time, configure clickable scenes for TestFlight testers, set card copy for official users, and confirm that the domain name association has not expired. The game team also wants to turn on Game Center capabilities, the subscription team wants to decide on a home sharing strategy, and the people responsible for publishing want to script version metadata, pricing, build associations, and review submissions.

The core change in this session is that App Store Connect begins to take over these post-release operational portals. App Clip builds will have a dedicated App Clip row in TestFlight; testers can directly launch the specified Invocation URL from TestFlight; before official release, developers must configure the default App Clip Card metadata on the iOS version page, and can also register advanced App Clip experiences for Apple Maps, NFC, QR code and other entrances. (04:33, 06:23)

Backend configuration starts to become part of the product process. Game Center challenges only require turning on a checkbox on the Game Center page in Features; the periodic ranking list has new start time, duration and repetition rules. Family sharing for in-app purchases and subscriptions is also turned on on the In-App Purchase detail page in App Store Connect, but live purchases cannot be turned off once enabled. (15:45, 19:00)

The final piece is automation. Apple previews new App Metadata APIs and Power and Performance APIs, totaling more than 200 new endpoints. The former can create App Store versions, set prices and available regions, edit metadata, associate builds, and submit for review; the latter can download the aggregated data behind the Xcode performance analysis tool. (20:13)

Detailed Content

App Clip from test URL to official card

(01:51) App Clip Invocation is the basic concept of this App Clip configuration. Users can trigger App Clips from Safari, Messages, Maps, NFC tag, QR code or location. Most triggering methods will bring an Invocation URL, which the system uses to determine which set of metadata to display on the App Clip Card; after the App Clip is launched, the same URL will be passed to the App Clip for deep linking to specific functions.

forestexplorer.org
camp.forestexplorer.org/reserve + campground ID
camp.forestexplorer.org/check-in + campground ID + campsite number

Key points:

  • The first URL corresponds to the App Clip Banner on the Safari page.
  • The second URL corresponds to entering the camp reservation scene from Apple Maps.
  • The third URL corresponds to scanning the NFC tag at the camp and entering the specific campsite check-in.
  • These are the three types of examples used in the transcript to illustrate Invocation URLs and are not official code snippets.

(04:33) The testing phase starts with build. App Clip cannot be packaged independently. It is built together with the complete App by Xcode and then sent to App Store Connect. Builds that include App Clip will have a new App Clip Invocation section in the TestFlight details. Developers can configure up to three Invocation URLs for testers. Each entry contains a title displayed in TestFlight and an Invocation URL, which takes effect immediately for testers after saving.

Key points:

  • TestFlight is the only App Clip invocation case in this presentation that does not display the App Clip Card first.
  • After the tester clicks the TEST button of TestFlight, the system will start the App Clip in the current build and pass the configured Invocation URL into it.
  • If a tester encounters an issue, TestFlight Feedback can collect feedback just like a regular app.

(06:23) When officially released, App Clip Card requires metadata. The default experience is configured on the iOS version page, including header image, subtitle and call to action verb. The default metadata is required for all App Clips. It will only be used for App Clips triggered by Safari and Messages.

Key points:

  • Safari page nameapple-itunes-appThe meta tag establishes the association between the page and the App Clip.
  • This meta tag will be added with the App Clip bundle ID attribute.
  • If the user is still on iOS 13 or earlier, the page can point to the full app’s App Store page via the app ID attribute.

(08:34) If an App Clip needs to display different cards by location or URL, you must register for advanced App Clip experiences. The Forest Explorer in the speech registers the complete URL for camp reservation and also uses URL prefix for campsite check-in, so that multiple campsites under the same campground share a set of metadata.

Key points:

  • Advanced experience allows you to customize App Clip Card metadata.
  • Advanced experience can connect to places on Apple Maps.
  • If the second half of the URL is just a specific resource ID, registering with a prefix can avoid repeatedly maintaining the same card for each resource.

(13:50) Finally, verify the domain name. Developers first use Associated Domains Entitlement to specify the domain names to be associated with App Clips, and then provide Apple App Site Association files on these domain names, which must reference the App Clip App ID. You can view domain validation status on the build details page of App Store Connect. Load Debug Status will access the server in real time and check the App Clip part of the file.

Key points:

  • cache status affects App Clip invocation on user devices.
  • When debugging the Apple App Site Association file, Load Debug Status is more straightforward than waiting for the cache to refresh.
  • This section shares many concepts with Universal Links, and this field also points to What’s new in Universal Links.

Game Center adds new challenges and cycle rankings

(15:45) Game Center challenges allow players to ask other players to complete an achievement or break a certain leaderboard score. Developers open it on the Features -> Game Center page of App Store ConnectAllow challenges in this game, players can challenge each other after saving.

Key points:

  • This is the switch in App Store Connect, not the GameKit code shown in the talk.
  • Challenges revolve around achievement and leaderboard score.
  • After the switch is saved, the ability will take effect on the player.

(16:12) Recurring Leaderboards are a new leaderboard type, used to collect scores within a preset period of time and open repeatedly according to rules. An example of a presentation starts for the first time on 13 October at 18:00, lasts 4 hours, and then repeats weekly.

start time: October 13, 6:00 pm
duration: 4 hours
recurrence: every week
active window: Tuesday 6:00 pm to 10:00 pm

Key points:

  • Added start time, duration and recurrence rules to the recurring leaderboard page of App Store Connect.
  • Each time it is opened repeatedly, a new ranking window will be generated.
  • This configuration is suitable for weekly tournaments, limited-time challenges and fixed-time events.

In-app purchase of family sharing into App Store Connect

(17:31) Apple announced that starting in the fall of 2020, subscription Family Sharing will be available to all app developers. It works for auto-renewal subscriptions as well as nonconsumable in-app purchases. After purchasing once, family members can share the same purchase.

Key points:

  • If the developer makes a subscription a family shared subscription, it can be designed as an upgrade to a personal subscription.
  • When family sharing is enabled, new buyers will automatically share with family members.
  • Existing subscribers need to actively opt in before they can share their current subscription with family members.

(19:00) The configuration entry is on the In-App Purchase detail page. The developer first checks the metadata and confirms that the page clearly states that this is a family shared in-app purchase, then clicks Turn On and confirms. Once enabled for live in-app purchases, it cannot be turned off.

In-App Purchase detail page
-> review metadata
-> Turn On
-> confirm
-> Family Sharing takes effect immediately

Key points:

  • metadata must indicate in advance that the purchased item will be shared by the family.
  • The switch of live purchase is irreversible and cannot be tested with online products.
  • It takes effect immediately after opening, suitable for confirming the upgrade path on the product strategy first.

App Store Connect API extended to release and performance data

(20:13) The App Store Connect API initially supports TestFlight, user management, provisioning, and reporting. Later in 2020, Apple plans to add two new APIs: App Metadata APIs and Power and Performance APIs, totaling more than 200 new endpoints.

App Metadata APIs:
- create new App Store versions
- set pricing and availability
- edit app and version-level metadata
- associate builds to App Store versions
- submit versions for review

Power and Performance API:
- download the aggregate data used by Xcode power and performance analysis tools

Key points:

  • App Metadata APIs open the maintenance process of App Store presence to automated scripts.
  • Power and Performance API is for downloading performance data, and the data source is consistent with the new analysis tools in Xcode.
  • This field only lists the scope of capabilities, and the specific walkthrough points to Expanding automation with the App Store Connect API.

Core Takeaways

  1. Make an App Clip Release Checklist. What to do: Put each Invocation URL, corresponding App Clip Card metadata, Apple Maps place association, and domain validation status into a pre-launch checklist. Why it’s worth doing: This Session clearly states that the URL will determine both the card metadata and the deep link after startup. The domain name cache status will also affect whether real users can invoke the App Clip. How to start: First list the Safari, Messages, Maps, NFC and QR code entries, then configure the test URL in TestFlight one by one, and use View Status and Load Debug Status to check the domain name before publishing.

  2. Conduct fixed time window activities for the game. What to do: Make weekly tournaments, weekend challenges, or limited-time leaderboards into Recurring Leaderboards and open Game Center challenges. Why it’s worth doing: App Store Connect already provides start time, duration and recurrence rules, and challenges can also be launched around achievement or leaderboard score. How to get started: Choose a low-risk leaderboard, set a first start time and duration, and set the activity pace to weekly or regular intervals.

  3. Change the subscription upgrade path to the family plan. What to do: Design a family shared subscription for an auto-renewable subscription that allows individual subscribers to upgrade to family sharing. Why it’s worth doing: The speech explains that new buyers will automatically share, existing subscribers need to opt in, and it is suitable for clear upgrade guidance. How to start: First check the subscription metadata to clearly tell the user that this is a shared purchase, and then enable Family Sharing on the In-App Purchase detail page.

  4. Expand the release script from build upload to metadata submission. What to do: Integrate creating App Store version, setting price and available regions, editing version metadata, associated build, and submitting for review into the same release pipeline. Why it’s worth doing: The goal of App Metadata APIs is to manage App Store presence and reduce web page operations before and after release. How to start: First split the release checklist into these resource actions, then read the API walkthrough of 10004, and add request and failure handling for each step.

  5. Transfer online quality data back to the team dashboard. What to do: Use the Power and Performance API to download the aggregated data behind the Xcode analytics tool and display it in the team’s existing quality dashboard. Why it’s worth it: One data source helps release owners see performance trends outside of App Store Connect. How to get started: Decide what power and performance metrics you want to track, then connect the API pull results to your existing dashboard or regression checking process.

Comments

GitHub Issues · utterances