Apple's design kit is on Figma. Build your own system.

Apple's official Figma profile is not new, but it is easy to forget how strange it is. For years, designing for Apple platforms meant working from community kits, which were careful and well-made best guesses at what Apple actually used. Now the source is Apple itself. The profile at figma.com/@apple carries official design kits for iPhone, iPad, Mac, Apple Watch, Apple TV, and Vision Pro, and each one gets updated as its operating system ships, right up to the current release. It is the most accurate reference we have ever had for these platforms. It is also the easiest to misuse, because a kit this good invites you to treat it as your design system, and it is not one.

What Apple actually gives you

Each kit is the platform's parts, drawn correctly: components and full views, the system interfaces, text and color styles, materials like blur and vibrancy, and layout guides that match the real safe areas. The first official kit arrived alongside iOS 17 in 2023, and the collection has grown to cover the rest of Apple's platforms since. To use one as intended you need the SF Pro font, which ships with macOS, and you have to accept Apple's license, which sets what you can and cannot do with the resources. What you get in return is a file that behaves like the platform instead of one that approximates it. A tab bar sits where a real tab bar sits. A sheet uses the real corner radius and the real material. The type ramp is the actual one and not a designer's memory of it.

Why the accuracy is worth having

An accurate reference raises the quality of what you can decide. A prototype built from the real components argues honestly. It shows the room how the thing will feel on a device, and it surfaces the places where your idea is fighting the platform before that fight ships to anyone. It also removes the dull work. Nobody should be rebuilding a tab bar or re-measuring the status bar by hand. Starting from the correct geometry means your hours go to the design that is actually yours instead of the design Apple already finished.

Where it goes wrong

Here is the trap. The kit gives you Apple's building blocks and Apple's defaults. It does not give you your product. It holds no opinion about your information architecture, your flows, your content, your brand, or the states that carry your specific edge cases. It cannot tell you whether something should be a segmented control in the first place, which is the real design question. The component only shows what one looks like after you have decided to use it. Teams that miss this build straight on top of the kit and ship something that looks like the demo and behaves like nobody made a decision. Every screen is technically correct and the whole is oddly generic, because the parts came pre-decided and the connective work, the part that is actually design, never happened.

How to use it well

So use it, and keep the line clear. The kit is your reference and your starting geometry. Your system is the layer you build on top of it: your own variables and styles, your components with your states, the decisions that make the product yours rather than a reskin of the platform. That layer is the whole argument of owning the system, not the screens, and it is exactly how the system this site runs on is built on top of its own foundations. Keep your own accessibility pass. The kit clears Apple's general bar for the platform, and that is not the same as your product's bar for the people who actually use it in their real conditions. Contrast, focus, and motion still have to be settled on your own screens. Watch the license, especially for anything you publish or ship commercially. And when the OS updates and the kit updates with it, treat that as a reason to re-decide rather than a patch to accept without looking, because a new default is still a default, and it is still not your decision.

Takeaways

Take the gift. An official, accurate, regularly updated reference for every Apple platform is a real improvement, and reverse-engineering Apple was never a good use of anyone's time. Then keep clear on what the gift is. It is the most correct set of parts you will find, and the parts were never the hard part. Building the layer that turns those parts into a product is where the real work is, and it is a large part of my design systems architecture work. What Apple published is the platform. What your users open is your product. The distance between those two is still yours to design.