Design in Figma.
Ship in your app.
A mobile design system that reaches the code. Change one token and the whole file follows, including the native iOS and Android components.
Branded platform components, tokens that ship as code, and Motion Foundations.
Full changelogOne source of truth. Everything you need.
A rebrand is one edit, not a sweep across every screen.
Tokens
Rebrand in minutes
Change the brand color once. Every component, both platform mirrors, light and dark, follow it. You do not reopen a single screen.
Apps examples
Ready-to-use screens
Real app screens built directly on the system. Token-connected, component-accurate starting points.
Platforms
Ship both platforms
Apple and Material conventions live together. No second library, no translation step.
Code handoff
Hand off without a spec
Your developer installs the token package and reads the exact values you designed with.
Dark mode
Get dark mode
Every component already has it, because color is a token and tokens have two modes.
AI agents
Brief an agent in one file
The free Core Skill tells Claude, Cursor and Figma which token to reach for.
Six screen groups, ready to open.
All in one pack.
1,972 components, one architecture.
Every one reads from the same tokens.
Four ways to work.
Changing path never means changing file.
Design once, ship both.
One neutral token set drives every screen on both platforms. Most projects start here and never need to leave.
Apple conventions, your brand.
System colours keep their accessibility behaviour. Only the accent carries your brand, so nothing about the platform breaks.
Material 3 with real values.
Material roles mapped to your brand, not a screenshot of the baseline. One dropdown returns the whole set to the untouched system.
Your agent reads the same file.
The Appetite Core Skill teaches any agent which token to use and which platform pattern to pick. Free, and it works with Claude, Cursor and Figma.
The token architecture is the real product. Everything else in the file is downstream of it.
The outputs I get from our designer are more understandable for development. I recommend it.
I now design systems and apps much faster and more efficiently. A great investment and a foundation for good app designs.
Appetite UI has helped us develop mobile apps much faster and more efficiently.
You may have seen this in the Figma community.
A teaser with the useful part removed is the industry standard. These are the opposite of that. Open the variables panel and the whole token chain is there, primitives resolving into semantic aliases, exactly as it works in the paid system. There are no refunds here, so the free files carry the risk instead.
See community profile
One payment. Yours forever.
No subscription and no seat maths.
Solo
$79
One designer, unlimited projects.
Team
$149
Up to ten people on one shared system.
All sales are final and there are no refunds. Open the free files first.
Questions worth asking.
Answered by the person who built it.
If you build for the web, dashboards or internal tools, this is the wrong file. If you need one screen for a pitch and will never open it again, take a free Community file instead. This earns its price when your file has to survive a rebrand or a second platform.
No. It runs on the free Figma plan. You only need a paid plan for Figma's own team library features.
Yes, on unlimited personal, client and commercial projects. You cannot resell or redistribute the system, or share the file outside your licensed team. Solo covers one designer, so agencies need Team.
Yes. It has shipped continuously since launch and 2.3 is current. Future versions cost you nothing. Read the changelog and judge the pace yourself.
Yes. Open the free files on Figma Community first. Same architecture at a smaller scale, so you can inspect the variables panel before you spend anything.