Questions, answered. Straight answers, no hedging.

Appetite UI is a Figma UI kit for mobile apps, built like a design system. It sits between the Apple and Material platform baselines and your brand: 237 components in 2,104 variants, all reading from 544 variables in one token source, and that same W3C DTCG source generates SwiftUI, Compose, Flutter and CSS. One-time license, $79 Solo, $149 Team, lifetime updates.

It is one, and it is more than one. You get 237 components in 2,104 variants and nine app flows you can open and build from today, which is what a kit is for. Underneath them, spacing, radius, elevation, type scale and color are defined once as tokens, and every component reads from those tokens. That second part is why the file is still consistent six months in, and why a rebrand is one edit rather than a sweep.

Untitled UI targets web products and SaaS. Appetite UI targets mobile apps, with the Apple and Material baselines built in. Different jobs, both good at theirs. If you are building for the web, buy Untitled UI. If you are building a mobile app, you are in the right place.

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.

Yes, by reference. Apple system colors and Material 3 roles are mapped through the Platform Bridge, and every mirror switches between your brand and the pure system baseline. Apple semantics keep their accessibility behavior, Material roles take your brand the way they were designed to.

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.

Anyone building for the web, a dashboard or an internal tool. This is a mobile kit, iOS and Android only, and something built for the web will serve you better. Anyone who needs a single screen for a pitch and will never open the file again, a free Community file does that for nothing. Buy it when the file has to survive a rebrand, a second platform, or a developer who wants the token values rather than a specification.

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 544 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.

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. The free Appetite Core Skill teaches agents which token and pattern to use, so Claude, Cursor and similar tools produce screens that read from your tokens instead of guessing values.

No. Appetite UI works on the free Figma plan. A paid plan is only needed if you want Figma's own team library features.

Duplicate the file and you are designing in it. There is no plugin, no account and no setup call. Setting your own brand color and type takes about ten minutes, because you are editing a handful of primitives rather than restyling components. The part that takes longer is deciding what your brand values should be, and no file can do that for you.

Then use the iOS mirror and ignore the rest. Nothing forces you to touch Material, and the Android side costs you nothing because it reads from the same tokens rather than duplicating them. The reason to have it in the file anyway is the day someone asks for an Android version, which in mobile tends to arrive sooner than planned.

$79 Solo, $149 Team. One payment, no subscription, and every future version included. The Team license is a single package for up to ten people rather than a price per seat.

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.

You can see the entire system before you pay. Four free files on Figma Community use the same token architecture at a smaller scale, and the full file has a read only preview, so nothing about it is hidden until money changes hands. Because of that there are no refunds. Open the free files first and decide from the file rather than from a promise.

Yes. Appetite UI has shipped continuously since launch, and every future version is included in what you already paid. The changelog shows the pace, so you can judge it 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.