iOS 27 and watchOS 27: What CarPlay, Apple Watch, and Wallet Changes Mean for Developers

Apple's pre-WWDC drumbeat is in full swing, and the 9to5Mac Daily recap for June 10, 2026 pulled together three threads that matter to anyone maintaining apps across iPhone, Apple Watch, and the car: CarPlay's overhaul in iOS 27, the feature set arriving in watchOS 27, and the next round of Apple Wallet changes. None of these are headline consumer features on their own, but together they reshape several frameworks developers have been building against for years.

This is a developer-facing breakdown rather than a feature tour. If you ship on both iOS and Android, the relevant question is always the same: what platform behavior changed, how does it hit your app, and what migration work does it create before the public release ships in the fall.

CarPlay in iOS 27: the layout finally catches up

CarPlay has lagged behind the rest of Apple's design language for several cycles. iOS 27 brings the interface in line with the broader visual refresh Apple has been rolling out, with a layout that adapts more aggressively to different screen sizes and aspect ratios. For most developers that is the operative detail. CarPlay screens are rendered by the system from templates you supply through the CarPlay framework, not by drawing your own UI, so a system-wide layout change can shift how your existing templates appear without any code change on your side.

If your app uses CarPlay app templates, now is the time to test every template type your app vends: lists, grids, now-playing, point-of-interest, and the navigation templates if you hold the entitlement. Template-based apps generally survive these transitions well because Apple owns the rendering, but spacing, truncation, and icon treatment can all change. The apps that break are the ones that assumed a fixed row count or relied on a specific number of grid items being visible at once.

The entitlement story has not changed. CarPlay categories like audio, communication, EV charging, parking, and navigation still require requesting the specific entitlement from Apple, and you still cannot test a navigation app without it. Plan entitlement requests early if you intend to ship a new CarPlay category alongside iOS 27.

watchOS 27: features worth wiring into your app

The watchOS 27 feature list is where the practical app work tends to concentrate, because the watch is the platform where Apple most frequently moves APIs. The recurring pattern with each watchOS release is that complications, workout APIs, and the relationship between the watch app and its iPhone counterpart all see incremental changes.

For complications specifically, anyone who has not yet migrated from the old ClockKit complications to WidgetKit-based complications should treat each new watchOS release as a reminder that the clock is running. WidgetKit is the supported path forward for watch face content, and it shares a programming model with the widgets you already build for iOS. That shared model is the upside: a team maintaining both platforms can reuse timeline logic rather than maintaining two parallel complication stacks.

If your watch app does anything with health or workouts, retest against the updated HealthKit and WorkoutKit behavior on the new build. Background delivery, workout session lifecycle, and the permissions prompts are the areas most likely to shift, and they are also the hardest to catch without a physical device. The watchOS simulator does not reproduce sensor behavior, so device testing is not optional here.

Apple Wallet in iOS 27: PassKit keeps expanding

The Apple Wallet updates round out the trio. Wallet changes are driven by the PassKit and WalletPasses frameworks, and each iOS release tends to widen what a pass can do, from richer pass content to new categories and tighter integration with system features like notifications and live updates.

For developers who issue passes, boarding cards, event tickets, loyalty cards, the work is usually on the server side as much as the app side. Passes are signed bundles generated by your backend, so supporting new pass capabilities means updating your pass generation pipeline and your signing certificates, not just your app binary. If iOS 27 introduces new pass fields or presentation styles, you get them by updating the pass.json structure and re-signing, which is a backend deploy rather than an App Store submission. That decoupling is genuinely useful: you can ship Wallet improvements to users on the current OS without waiting on an app review cycle.

The cross-platform reality

None of this has a direct Android equivalent, and that is precisely the maintenance tax of shipping on both platforms. CarPlay maps loosely to Android Auto, but the template models differ enough that code does not transfer. Apple Watch has no Android counterpart that shares an API surface with Wear OS. Wallet passes overlap conceptually with Google Wallet, but the pass formats and signing models are separate implementations.

The pragmatic approach is to treat these as platform-specific surfaces with their own release calendars. iOS 27, watchOS 27, and the Wallet changes will land together in the fall, which means the testing window opens with the developer betas at WWDC. A team that waits until the public release to test CarPlay templates and watch complications is a team that ships a regression. Get the betas onto real hardware as soon as they are available, exercise every template and complication your apps vend, and update your pass generation pipeline in parallel so the backend is ready when the OS ships. The full breakdowns of each feature set are worth reading on 9to5Mac as Apple's documentation fills in over the beta period.