Questions, answered. Straight answers, no hedging.

Appetite UI is a Figma UI kit for iOS and Android apps, built like a design system. One token source drives Apple and Material components in light and dark mode, and exports to SwiftUI, Jetpack Compose, Flutter and CSS. It sits between the Apple and Material platform baselines and your brand: 174 components and 1,984 variants, reading from 589 variables in 6 collections. One-time license, Solo, Team or Enterprise on request, with lifetime updates; the prices are on the pricing page.

Yes. You get 174 components and 1,984 variants, plus ten app flows you can open and build from today, which is what a kit is for. Underneath them, spacing, radius, type scale, color and motion 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 is built for web apps, dashboards and marketing sites. Appetite UI is built for iOS and Android apps, with the Apple and Material baselines in one file. If you are building for the web, buy Untitled UI. If you are building a mobile app, you are in the right place.

Use Apple's kit if you ship on iOS only and want Apple's exact components. Use Appetite UI when the same app also ships on Android, or when your brand has to sit on top of the system. Its iOS mirror keeps Apple's system colors and their accessibility behavior, so you are not giving up the platform.

One that keeps both platforms on one token source. Apple's kit covers iOS and iPadOS and Google's Material 3 kit covers Android, one platform each, so an app on both means two systems with different role names. Appetite UI holds an iOS 27 mirror and a Material 3 mirror in one file, both reading the same 589 variables, and its Platform Bridge has a System mode that returns each screen to the values Apple and Google publish.

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 code output for SwiftUI, Compose, Flutter and CSS.

Anyone shipping web, dashboards or internal tools. This is iOS and Android only, and a kit built for the web will serve you better. Anyone who needs one screen for a pitch and will never reopen the file should take a free Community file instead. Buy it when the file has to survive a rebrand, a second platform, or a developer who wants the values, not a spec.

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, type and motion live in 6 token collections and 589 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, and the source and all four outputs come with the file you buy. Your developer adds them to the project 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.

The tokens do. The file you buy includes the token source as W3C DTCG JSON and its generated SwiftUI, Jetpack Compose, Flutter and CSS outputs, with the same names as the Figma variables. React Native reads the JSON source through a token pipeline. The components themselves are Figma components; coded components are not part of the file.

No. Code Connect maps one Figma component to one code snippet. Appetite UI writes the decisions an agent needs onto the variables themselves, their code names for web, iOS and Android, and the Core Skill tells the agent which token to reach for, which a mapped snippet never decided.

Yes. The Appetite UI Core Skill, included in the file you buy, 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.

Yes. Light and dark mode switch through Figma's variable modes, which need a paid Figma plan, and so does publishing the file as a team library.

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.

Yes. The Apple pages follow iOS 27 in the switch and slider, the tab bar, the status bar and the action sheet, and carry Liquid Glass at Clear, Regular and Tinted, the Dynamic Island and the iPhone Duo chrome. The Android side follows Material 3.

One payment, no subscription, and every future version included. Solo covers one designer and Team is a single package for up to ten people rather than a price per seat; both prices are on the pricing page. Enterprise has no public price. Write to hi@appetiteui.com.

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 a Team license.

No. You can see the entire system before you pay: the full file has a read-only preview in Figma, and the docs state every token and component. Open the preview 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 latest release, in October 2026, added iPhone Duo, Dynamic Island, charts and tables, a Tasks app flow, animated components and Liquid Glass in three styles. The changelog shows the pace, so you can judge it yourself rather than take a promise.

Appetite UI started as the in-house UI kit of the bpolacek.cz studio, which designs mobile apps for startups, and grew into a product. It is built with the studio team and external collaborators, and questions sent to hi@appetiteui.com reach the people who build it.

Yes. Open the read-only preview of the full file in Figma. It is the whole system, every component and app screen, so you can see exactly how it is built before you spend anything.