The decisions behind the file, written down.
Where Appetite UI fits against the other Figma kits, how one token source becomes SwiftUI and Compose, and what an agent reads in Figma or in Appetite UI Code.28 articles, updated
Side by side
The short answer, one page each.
Decision pages with a dated table and the sources they read. The articles above are the long answer.
Appetite UI and Apple's iOS 27 UI kit
One platform and its exact components, or one file for iOS and Android, side by side.
Appetite UI and the Material 3 Design Kit
Google's baseline for Android, or Material roles that carry your brand on iOS too.
Appetite UI and Untitled UI
A web kit and a mobile kit, side by side on the screens where they differ.
Appetite UI and Dynamic Layer
Two mobile kits, compared on the rebrand, the second platform and the code.
Figma UI kits for mobile apps
The other files people weigh for iOS and Android, each in its own words.
How to choose a Figma UI kit for an iOS app
Ten questions to ask of any kit, each with a five minute test in Figma.
Enough reading. Open the file.
The articles explain the decisions. The kit is where you can watch them work.





















































