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.
Not an alternative to Apple and Material. Appetite UI is the layer every guide tells you to build by hand.
Your app
SwiftUI, Jetpack Compose, Flutter, or the web. They are installed from a token package, so the build cannot deviate from the design. The implementations support AI capabilities.
Appetite UI
Your brand as a connected token architecture, mapped onto both platform languages. This is the layer everyone tells you to build by hand.
Apple iOS 26 and Material 3
The platform baselines, untouched. Their accessibility behaviour and conventions stay exactly as Apple and Google intended them.
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.
Six screen groups, ready to open. All in one pack.
1,972 components, one architecture. Every one reads from the same tokens.
The token architecture is the real product. Everything else in the file is downstream of it.
Jacob Engelbreth
Digital Concept Developer
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 seats on one shared system.
Questions worth asking. Answered by the person who built it.
No. A kit gives you components. A system gives you the decisions underneath them. Spacing, radius, elevation, type scale and color are defined once as tokens, and every component reads from those tokens. Change a token and the whole system moves with it. That is the reason your file is still consistent six months in.
Yes, and the reason is architecture rather than volume. Large products fail design systems in two places: a rebrand and a second platform. Appetite UI holds both. Color, spacing, radius, elevation and type live in 6 token collections and 401 variables, so a brand change is one edit rather than a sweep across screens. Both platform languages sit in the same file, so adding iOS or Android is not a second library. Every component already carries light and dark. The Team license covers ten seats on one shared source of truth, and every future release is included, so the system does not age out from under you.
Use both. Every guide tells you to start from the Apple and Material kits and build your own system on top of them. Appetite UI is that layer, already built. The platform baselines stay untouched, including their accessibility behavior, and your brand sits inside them.
A free file gives you a sample of components and stops at the surface. Appetite UI gives you the connected layer underneath: a full primitive to semantic token architecture, dark mode on every component, both platform languages in one place, application screens, motion tokens and installable code output.
No. Appetite UI works on the free Figma plan. A paid plan is only needed if you want Figma's own team library features.
Yes. Personal, client and commercial projects, unlimited. What you cannot do is resell, sublicense or redistribute the system, or share the file outside your licensed team. The license sets out the full terms. The Solo license covers one designer, so design teams and agencies need the Team License.
One W3C DTCG source generates CSS, SwiftUI, Jetpack Compose and Flutter. Your developer installs the package and reads the exact values you designed with, so the build cannot drift from the design. The SwiftUI output emits Dynamic Type anchors rather than point sizes, and the Compose output includes a ready Material 3 typography object.
Yes. Appetite UI has shipped continuously since launch and 2.3 is current. Every future version is included in what you already paid. The changelog is on this page so you can judge the pace yourself rather than take a promise.
Yes. Start with the free files on Figma Community. They use the same architecture at a smaller scale, so you can open the variables panel and see exactly how the system is built before you spend anything.