Appetite UI
Figma UI kit for mobile apps that’s fast, flexible and real
8 followers
Figma UI kit for mobile apps that’s fast, flexible and real
8 followers
Appetite UI is a mobile design system for Figma, not a pile of screens to cherry-pick from. 1,930 components and 380+ variables across 6 collections, so you start at screen level instead of rebuilding buttons.
iOS and Material patterns live inside the system and take your brand, instead of being copied out of Apple and Google files. Tokens leave Figma as JSON, with docs your developers and your AI tools can read.
One payment, lifetime updates, solo and team licenses.
This is the 3rd launch from Appetite UI. View more
Appetite UI Code
Launching today
Appetite UI Code brings the Appetite UI kit to React Native (Expo), SwiftUI, Flutter and Jetpack Compose. Components keep the names, variants and tokens of the Figma kit, so a Figma variant maps to a prop. Brand color, radius and font live in one theme file. React Native ships every component plus an App Starter with Tasks, Foodie and AI flows; the native stacks start with the core set. Agent kit for Claude Code and Cursor. One payment, every release included.
Payment Required
Launch Team / Built With
TinesThe single, secure environment for agents, apps, and automations.
Promoted
Hey Product Hunt, Bob here.
I design mobile apps, and Appetite UI is the Figma kit my team and I built for iOS and Android apps: one token source, light and dark, Apple and Material components in one file.
Appetite UI Code puts the same system into code: React Native with Expo, SwiftUI, Flutter and Jetpack Compose.
What you get:
- The names and variants from the Figma file, so a Figma variant maps to a prop
- Brand color, radius and font in one theme file, and every component follows
- An App Starter on Expo Router with Tasks, Foodie and AI flows, in light and dark
- An agent kit (AGENTS.md, CLAUDE.md, a skill and Cursor rules), so Claude Code and Cursor build with the components instead of inventing new ones
- Source code you own. Only the theme core installs as a package
Where it stands today: React Native has every Appetite UI component. SwiftUI, Flutter and Compose start with the core components, and every release adds more. You pay once, every release after your purchase is included, and the price goes up with each release.
You don't need Figma to use it. If you want to look at the code first, the free base is on GitHub.
Which stack do you build in, and which component should land next in it?
SwiftUI for me — and the agent kit is the part that caught my eye. I use Claude Code a lot, and the thing that breaks my flow is the agent inventing its own components instead of using the ones in the design system. If the SwiftUI set keeps the same variant-to-prop mapping, that's the bit I'd actually trust it with. Which core components are in the SwiftUI set today?