Apple releases iOS 27, iPadOS 27, and macOS 27 'Golden Gate' design kits

Apple released its official design resources for iOS 27, iPadOS 27, and macOS 27 on its developer portal this week, with 9to5Mac flagging the drop. The desktop edition carries the internal codename "Golden Gate." Within an hour, design leads in studios from San Francisco to Berlin were dragging the Sketch and Figma files into their working folders.

For designers outside Cupertino, this is the first concrete window into the new system language. The kits ship as Sketch and Figma files and typically include the type ramps, color tokens, and component templates that match what the OS will actually render on shipped hardware.

What do Apple's design kits actually contain?

Apple has shipped developer-facing UI kits under this program for over a decade, in formats that grew from Photoshop templates to today's vector source files. A designer opening the new package scans for the same anchors they always check:

• Symbol sets covering navigation, modals, controls, and system bars
• The current SF Pro type family at every size the system uses
• Color tokens for both light and dark appearances
• Device frames for iPhone, iPad, and Mac
• Icon templates in vector and raster formats

The specifics for iOS 27, iPadOS 27, and macOS 27 aren't yet public beyond the listing itself. Designers who download the kit in the next day or two will be the first to catalog what shifted from last year.

What's the "[U]" tag about?

9to5Mac appends "[U]" when an item receives an update after original publication. The marker suggests the resource listing — or the page surrounding it — was revised at least once before capture. Apple occasionally refines its design files in the hours after first release, typically correcting template dimensions or swapping placeholder iconography that didn't quite line up.

For most designers the distinction matters little. They pull the latest file before starting work.

Why does the codename matter?

"Golden Gate" keeps Apple's desktop naming cycle on California geography, following "Sequoia." The codename tends to leak months ahead of the marketing name that Apple reveals at WWDC each June, and designers who build launch materials often adopt it early for their pitch decks, splash screens, and product mockups.

Beyond branding, the codename itself changes nothing in the kit. It signals only which year's macOS the templates target, and which set of system components the controls map against.

Who actually uses these files?

The audience splits into three working groups. iOS-first shops pull the kit when a client wants to see a future device mockup months ahead of release. Cross-platform teams rebuild their component libraries against the new tokens each fall. Indie developers download the files to check whether their existing patterns still fit the year's proportions, then decide whether to adjust.

Each group treats the kit as a starting point, not gospel. Apple's own first-party apps often ship with custom UI that drifts from the templates within weeks of release.

What comes next?

The next beat in this cycle is the SDK release, which usually follows at WWDC alongside the first developer beta. Designers who work ahead of the SDK treat the resource drop as their working brief — they can mock up screens, set proportions, and pitch concepts without waiting for a working build of the OS.

For now, the kit is in the wild. The first design diffs will surface on design Twitter and Figma community boards within hours, and someone will spot a corner radius change before the day ends.