Localising Apps With Agents in Xcode 27

David Caddy | Published July 20, 2026

Abstract Xcode localization workflow illustration

Localisation looks like one of the more useful jobs for Xcode 27's coding agents. Apple's localisation guide describes how they can add languages, update string catalogues, and translate text, including the plural forms a language needs.

Xcode builds all targets to collect localisable strings and can also translate user-facing text in your app's information property list. The strings need to use localisable APIs for Xcode to find them, so missing text may need a change in your code before translation. For a small developer, getting that preparation and a first translation pass done could make it easier to find time for localisation alongside feature work and bug fixes.

The ability to supply your own guidance is particularly useful. Apple suggests putting it in a TRANSLATION.md file and referring to that from your agent's AGENTS.md or CLAUDE.md. You can include a glossary, product names to leave alone, and the tone you want. That gives you somewhere to record decisions about your app's language instead of explaining them again with each request. Apple's WWDC session covers the translation workflow in more detail.

There's still review work to do. Apple recommends testing the translated app, checking that text fits and right-to-left layouts work, and getting feedback from people who speak the language and live in the region. A translation that reads plausibly to someone who doesn't know the language is a poor measure of whether it's any good.

That's why I find this use of agents appealing. The preparation is repetitive, and the output gives you something specific to review with a translator or a tester. If it reduces the time needed to reach that point, it could help more small apps support another language.

Siri Needs Better Data Sources

David Caddy | Published July 14, 2018

Poor ol’ Siri has had a lot of criticism in recent years and unfortunately almost all of it has been well justified. Hopefully the recent announcement that former Googler John Giannandrea is taking over as head of the machine learning and Siri teams at Apple will mean good things for the beleaguered virtual assistant’s future. For now though, let’s face it, when compared to the competition (notably Google’s Assistant and Amazon’s Alexa) Siri is just plain average.

One aspect of Siri’s struggles that doesn’t get much attention is the sub-par data sources it has has to draw on. While it is admittedly difficult to go up against the data king, Google, in this space, sometimes mistakes are laughable and completely undermine any confidence one might have in Apple’s vocal helper.

One example first discovered by my dear mother towards the end of last year is Apple’s mistaken belief that the upcoming Grand Final Friday public holiday for the Australian state of Victoria is on October 5, which is presented to users as fact both through Siri interactions and via the company’s built-in calendar application. The correct date however, is September 28, as is listed by Google and every other reputable source of public holiday information.

In an effort to help out the Silicon Valley giant — and anyone planning a vacation around the holiday — I reached out to Apple’s Twitter support team in early February with details of the issue and was told it had been “forwarded to the proper team for investigation”. Sadly it seems that investigation has gone nowhere, leaving the Apple-toting contingent of the 6,358,900 people that call Victoria home having to wait an extra week for their next day off.

You need to do better Apple, please fix this and give Siri the resources it needs to succeed.