Skip to main content

Apple commits to replacing non-inclusive terms across its developer ecosystem

Joining a wider industry shift, Apple announced that it is working to replace exclusionary language in its developer documentation and APIs with alternative terminology.

Renaming things takes time and effort as large parts of infrastructure have to migrate in response. For third-party developers in the App Store, Apple will be changing the names of APIs used in their code where appropriate, which will also necessitate engineering work to migrate.

Examples of exclusionary terminology include using a noun like ‘master’ to describe the primary code repository. Apple’s source control features in Xcode, starting with Xcode 12, now names the default branch ‘main’ by default. Github and other companies announced similar policy changes earlier this year.

Similarly, Apple is replacing the usage of ‘whitelist’ and ‘blacklist’ in its documentation with ‘allow list’ and ‘deny list’, to eradicate possible discriminatory connotations. These phrases have long-established technical definitions, but changing to alternative words removes any possibility of confusion or misinterpretation.

As a company, Apple is auditing its frameworks for similar language that warrants adjusting. Developers can expect to see the introduction of renamed APIs in future versions of iOS 14, macOS Big Sur, and the like.

FTC: We use income earning auto affiliate links. More.

iPhone SE case- Griffin Survivor
You’re reading 9to5Mac — experts who break news about Apple and its surrounding ecosystem, day after day. Be sure to check out our homepage for all the latest news, and follow 9to5Mac on Twitter, Facebook, and LinkedIn to stay in the loop. Don’t know where to start? Check out our exclusive stories, reviews, how-tos, and subscribe to our YouTube channel

Comments

Author

Avatar for Benjamin Mayo Benjamin Mayo

Benjamin develops iOS apps professionally and covers Apple news and rumors for 9to5Mac. Listen to Benjamin, every week, on the Happy Hour podcast. Check out his personal blog. Message Benjamin over email or Twitter.