Category: Apple Developer News

A recent injunction issued by a district court suspended enforcement of Texas state law SB2420, which introduced age assurance requirements for app marketplaces and developers. In light of this ruling, Apple will pause previously announced implementation plans and monitor the ongoing legal process.

The tools we previously announced to help developers meet their compliance obligations will remain available for sandbox testing, including:

These tools can also be used to help developers with their obligations under laws coming into effect in Utah and Louisiana in 2026. The Declared Age Range API remains available worldwide for users on iOS 26, iPadOS 26, and macOS 26, or later.

To comply with the Mobile Software Competition Act (MSCA), Apple is introducing changes to iOS that create new options for developers’ apps in Japan. Beginning with iOS 26.2, developers can distribute apps on alternative app marketplaces, operate alternative app marketplaces, process app payments for digital goods and services outside of Apple In-App Purchase in iOS, and more.

The new options for downloading apps from alternative app marketplaces and making app payments open new avenues for malware, fraud, scams, and privacy and security risks. Apple has worked with Japanese regulators to introduce protections from these new threats — with a special emphasis on the safety of younger users. Those protections include Notarization for iOS apps, an authorization process for app marketplaces, and requirements that help protect children from inappropriate content and scams.

By March 17, 2026, all current members of the Apple Developer Program will need to agree to the latest update to the Apple Developer Program License Agreement, which includes new terms that allow for these options in Japan.

Learn more about the updates

You can also request a 30-minute online appointment to ask questions about these changes.

Beginning December 10, 2025, a new Australian law will require certain social media platforms operating in Australia to prevent people under 16 from having a social media account. Impacted developers are responsible for making sure they follow the requirements of the new law, including deactivating any existing accounts for users under 16 and monitoring new signups.

Apple provides several tools to help meet the requirements of this law:

Declared Age Range API

The new Declared Age Range API helps developers provide age-appropriate experiences for their users. Developers can choose to request the age range that is most relevant to their use case, such as an age range of under 16, and modify app behavior based on this information.

App description on the App Store

When making an app available on the App Store, developers must include a description that helps users determine whether the app is appropriate for them. Developers can use this app description field to indicate information that may not be captured in other areas of the product page, such as social media age restrictions for people under a certain age.

In-app controls on the App Store product page

This year, Apple updated the age ratings questionnaire that is required for all apps. The update included adding new questions about in-app controls, such as the presence of age assurance and parental controls. Apps using age assurance methods — such as the Declared Age Range API — to comply with the law and prevent users under 16 from creating accounts can indicate the presence of this capability on their App Store product page.

Higher minimum age rating

With our recent update to age ratings, developers can set a higher age rating than the one generated by their responses to the age ratings questionnaire in App Store Connect. Developers can view the age rating for each of their apps and select a higher rating if they wish, in the App Information section in App Store Connect.

Age Suitability URL

When updating an app’s age rating, developers have the option to include an Age Suitability URL that links to a developer-hosted website with details about the app and its age-related content. When enabled, this URL appears on the App Store product page under the age ratings details section. Developers can use this URL to provide region-specific information and requirements, such as the prohibition in Australia of people under 16 having a social media account.

Learn more about the Declared Age Range API

Learn more about updating your app’s age rating

Learn more about an app’s product page

In this edition:

• Meet the 2025 App Store Award winners.
• Sign up for new design and Liquid Glass activities in the new year.
• Check out the latest additions to our ever-expanding video library.
• Meet the team behind the sticker-centric language-learning app CapWords.
• Browse new documentation and HIG updates.

Read the full story

Every year, the App Store Awards celebrate exceptional apps and games that improve people’s lives while showcasing the highest levels of technical innovation, user experience, design, and positive cultural impact. This year, the App Store Editorial team is proud to recognize 49 outstanding finalists. Winners will be announced in the coming weeks.

Learn about the finalists

Today, we’re introducing the Mini Apps Partner Program, which expands on the App Store’s ongoing support for apps that offer mini apps. Mini apps are self-contained experiences that are built using web technologies like HTML5 and JavaScript. This program is designed to help developers who host mini apps grow their business and further the availability of mini apps on the App Store — all while providing a great customer experience.

Participating developers may benefit from a reduced commission rate of 15% on the sales of qualifying In-App Purchases. To be eligible for this reduced commission rate, participating apps must support certain App Store technologies, including the Declared Age Range API and the Advanced Commerce API in order to help provide a safe and seamless experience for customers of all ages.

Learn more about the Mini Apps Partner Program and eligibility

The App Review Guidelines have been revised to support updated policies and to provide clarification. Please review the changes below:

• 1.2.1(a): This new guideline specifies that creator apps must provide a way for users to identify content that exceeds the app’s age rating, and use an age restriction mechanism based on verified or declared age to limit access by underage users.
• 2.5.10: This language has been deleted (“Apps should not be submitted with empty ad banners or test advertisements.”).
• 3.2.2(ix): Clarified that loan apps may not charge a maximum APR higher than 36%, including costs and fees, and may not require repayment in full in 60 days or less.
• 4.1(c): This new guideline specifies that you cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer.
• 4.7: Clarifies that HTML5 and JavaScript mini apps and mini games are in scope of the guideline.
• 4.7.2: Clarifies that apps offering software not embedded in the binary may not extend or expose native platform APIs or technologies to the software without prior permission from Apple.
• 4.7.5: Clarifies that apps offering software not embedded in the binary must provide a way for users to identify content that exceeds the app’s age rating, and use an age restriction mechanism based on verified or declared age to limit access by underage users.
• 5.1.1(ix): Adds crypto exchanges to the list of apps that provide services in highly regulated fields.
• 5.1.2(i): Clarifies that you must clearly disclose where personal data will be shared with third parties, including with third-party AI, and obtain explicit permission before doing so.

Translations of the guidelines will be available on Apple Developer website within one month.

In this edition: Catch the new design in the wild, and let Apple experts show you how to quickly and easily bring it to your apps. Plus, get the latest on the Swift Student Challenge 2026, and check out new developer videos available on demand.

Also, explore new activities all over the world, get your apps and games ready for the holidays, and browse the latest news, documentation, and Technotes.

Read the full story

Today we’re releasing more details about the tools we’re making available for developers to help them meet their compliance obligations under upcoming U.S. state laws, including SB2420 in Texas. While we’re providing these tools to help developers navigate the evolving legal landscape, Apple remains concerned about the potential implications of laws like SB2420 in Texas. Specifically, we worry they could undermine the privacy of all users by requiring the collection of sensitive personal information just to download an app – even those that simply provide weather forecasts or sports scores.

Starting January 1, 2026, new Apple Accounts in Texas will be subject to new requirements. This includes age assurance and parent or guardian consent on behalf of minors under the age of 18 for downloads, purchases, and significant changes associated with an app. Parents or guardians will also be able to revoke their consent for any app they previously approved.

To meet their obligations under the law, developers may need to adopt new capabilities to receive age category information, trigger consent for a significant change, and learn when a parent or guardian revokes their approval for a child or teen to use their app. Developers can use the following APIs available in the beta versions of iOS 26.2 and iPadOS 26.2 to help them meet their obligations. Sandbox testing is also available to help test the user experience when implementing these APIs to comply with Texas state law.

Age category information

Developers can use the updated Declared Age Range API to obtain a user’s age category, which is defined by Texas state law as under 13, 13-15, 16-17, or over 18. Age categories for users with new Apple Accounts in Texas as of January 1, 2026, will be shared with a developer’s app when they request it. The API will also return a signal from the user’s device about the method of age assurance, such as credit card or government ID, and if consent is required when there’s a significant change to an app.

Obtaining consent for significant changes

Certain types of changes to an app may be considered significant changes under age assurance laws, such as Texas SB2420. It’s the developer’s responsibility to determine when there’s a significant change to their app.

When a developer determines they have made a significant change to their app, they’ll need to use the Significant Change API under the PermissionKit framework to ask the parent or guardian to provide consent for the child or teen to continue using the app or new feature within the app. When the API is called, the child or teen user will see a system dialog to request parental consent and developers can restrict access until consent is obtained.

Texas state law considers a change in the age rating of an app to be a significant change, and developers should keep their age rating selections current in App Store Connect. When a developer updates their app’s age rating, the rating is updated on all user devices once the version is live. Developers can use a new property type in StoreKit to automatically check when their app’s age rating has changed on a user’s device and then use the Significant Change API to request parental consent.

App consent revocation

A parent or guardian in Texas can withdraw consent for any app, which will block launching of the app on the child or teen’s device. The App Store will provide a server notification that developers can configure to receive notifications that the parent or guardian has withdrawn consent for their app on a child or teen’s device.

Sandbox testing

Sandbox testing is now available for the Declared Age Range API and Significant Change API in the beta versions of iOS 26.2 and iPadOS 26.2.

Next steps

1. Review documentation and implement the following:

2. Use Apple’s sandbox testing environment to validate that the APIs have been implemented correctly.
3. When the Release Candidates of iOS 26.2 and iPadOS 26.2 become available, submit your apps to App Store Connect so users can update their devices with your updated apps with the customer releases.
4. Stay tuned for additional communication about future tools to help developers meet upcoming legal obligations in Utah, Louisiana, and Brazil.

The App Store is designed to make it easy to sell your digital goods and services globally, with support for 44 currencies across 175 storefronts.

From time to time, we may need to adjust prices or your proceeds due to changes in tax regulations or foreign exchange rates. These adjustments are made using publicly available exchange rate information from financial data providers to help make sure prices for apps and In-App Purchases stay consistent across all storefronts.

Price updates

Beginning November 17:

Pricing for apps and In-App Purchases will be updated for Poland, Switzerland, and Türkiye if you haven’t selected one of these storefronts as the base storefront for your app or In‑App Purchase.¹

If you’ve selected Poland, Switzerland, or Türkiye as the base storefront for your app or In-App Purchase, prices won’t change. On other storefronts, prices will be updated to maintain equalization with your chosen base price.

Prices won’t change in any region if your In‑App Purchase is an auto‑renewable subscription. Prices also won’t change on the storefronts where you manually manage prices instead of using the automated equalized prices.

The Pricing and Availability section of Apps has been updated in App Store Connect to display these upcoming price changes. As always, you can change the prices of your apps, In‑App Purchases, and auto‑renewable subscriptions at any time.

Learn more about managing your prices

View or edit upcoming price changes

Edit your app’s base country or region

Pricing and availability start times by country or region

Set a price for an In-App Purchase

¹ Excludes auto-renewable subscriptions.