Comparison

Pick the kit by where your app ships in 2026.

iPhone only, Android only, the web or both: each answer points to a different Figma kit.7 kits, updated November 2026

At a glance

Which kit does what, check by check?

Nine checks for one app on iOS and Android, each read on the maker's own page. A ring means the page does not say, which is not the same as the kit lacking it.Every kit checked on its own site on October 14, 2026

Figma UI kits against nine checks for an app on iOS and Android, read on October 14, 2026
Kit	iOS and Android	Apple and Material	One system	Dark as a mode	Brand variables	Tokens	Component code	Screens	Preview
Appetite UI	iOS and Android: Yes. iPhone, Android phones and iPhone Duo, on 20 Platform variables in five modes: ios-md, ios-lg, android, ios-duo-outer and ios-duo-inner.	Apple and Material components: Yes. 20 pages of Apple components and 17 of Material 3 components, each drawn to its own platform's conventions: 67 Apple and 44 Material component sets.	One system for both: Yes. Both component sets read one token set through the Platform Bridge, 113 variables (53 Apple and 60 Material slots), so iOS/tintColor and M3/sys/color/primary end on the same brand token. The Platform mode switches touch targets, bar heights and corners, 44 pt on iOS and 48 dp on Android. Bars, sheets and the primary action are drawn once per platform.	Dark as a variable mode: Yes. Light and Dark are two modes of the 190 Color Tokens, so a frame switches with one setting.	Brand in variables: Yes. The brand color is written once, in brand/base. Repointing it recolored 1,110 layers across components, app screens and charts, on both platforms and in both modes, counted in the file on October 8, 2026.	Token values for code: Yes. One token file in the W3C Design Tokens format, with SwiftUI, Jetpack Compose, Flutter and CSS outputs, in the file you buy.	Component code: Yes. Appetite UI Code ships every component in React Native, with an App Starter, and the core set in SwiftUI, Flutter and Jetpack Compose. The Figma file also exports token values.	App screens: Yes. App screens for finance, booking, fitness, social, AI, tasks and more in light and dark, and iPhone Duo pairs for 8 apps, built from the same components.	Look before paying: Yes. A read-only preview of the whole file, and public docs for every token and component.
Apple's iOS and iPadOS 27 UI kit	iOS and Android: No. Its license grants use "solely for creating mock-ups of user interfaces designed for use in software products that run only on Apple's macOS, iOS, watchOS, tvOS, and/or visionOS operating system software", so not for Android.	Apple and Material components: Not on its page. Not on its page: Apple names "components for all common controls and views" for "iPhone and iPad design comps and user flows" and no Material components.	One system for both: Not on its page. One platform, so nothing switches between two.	Dark as a variable mode: Not on its page. Apple's text lists "text styles, color styles, and materials" and does not say how dark mode switches.	Brand in variables: Not on its page. Its page names color styles and no variables or tokens for a brand.	Token values for code: Not on its page. Apple lists the kit as a Figma and a Sketch download and names no token export.	Component code: Not on its page. No code is named on its pages.	App screens: Yes. The kit contains "design templates" beside its components.	Look before paying: Yes. A Figma Community file anyone can open, with no price on any of Apple's pages.
Google's Material 3 Design Kit	iOS and Android: Not on its page. Its changelog says "Material Android is Compose-first. Use this design kit for Jetpack Compose." and names no iOS use.	Apple and Material components: Not on its page. Not on its page: it names "styles and components to help you get started" for Material Design 3 and no Apple components.	One system for both: Not on its page. One platform, so nothing switches between two.	Dark as a variable mode: Yes. Its changelog lists "Variables added: color, typography, and state layers", and the Material Theme Builder plugin switches the light and the dark theme.	Brand in variables: Yes. The Material Theme Builder plugin will "generate a theme (material-theme) and Material Design tokens as Figma styles" from your color.	Token values for code: Yes. The plugin exports the theme: "Click Export and select your desired code format."	Component code: Yes. Its changelog lists "Jetpack Compose Code Snippets" in the file.	App screens: Yes. Its changelog for V1.16 (06.24.24) lists "Example screens" under "Additions", beside "Variables added: color, typography, and state layers".	Look before paying: Yes. A Figma Community file anyone can open, "Licensed under CC BY 4.0", with no price on its page.
Dynamic Layer	iOS and Android: Yes. Its page offers "polished iOS and Android screen templates" and says "Whether you want to design iOS, Android or hybrid apps".	Apple and Material components: Not on its page. Its pages name iOS and Android templates and do not name Apple or Material components.	One system for both: Not on its page. Its templates page lists one set of screens with no platform split, and no platform switch is named.	Dark as a variable mode: Yes. Its docs say "If you change the mode to Dark, the background color also changes to grey-800", and its Figma page says "Switch between Light and Dark Mode".	Brand in variables: Yes. Its Figma page says "Scale your Design System with Tokens", for "colors, spacing, font styles or radius".	Token values for code: Yes. Its Flutter library is "token-driven", with "Token-based foundations (colors, spacing, radius, typography)" in Flutter.	Component code: Yes. Its plans include "Flutter Code"; its docs also describe SwiftUI and Jetpack Compose versions.	App screens: Yes. Screen templates such as welcome, login, sign up, paywall, inbox and settings.	Look before paying: Yes. A free plan: "Try Dynamic Layer with selected components".
Xela UI	iOS and Android: Yes. Its Figma kit is for "desktop & mobile apps", and its code packages target iOS ("Swift 5+, SwiftUI, iOS 13+") and Android ("Jetpack Compose").	Apple and Material components: Not on its page. Its pages name no Apple or Material components in the Figma file.	One system for both: Not on its page. The code is sold as one package per platform; how the Figma file relates the two is not stated.	Dark as a variable mode: Not on its page. Its page says "Toggle between dark & light" and does not say how.	Brand in variables: Not on its page. Its page lists "Color Tokens" among its sections and does not say that a rebrand runs through variables.	Token values for code: Not on its page. No token export is named.	Component code: Yes. A design and code bundle "with Figma, React, Flutter, SwiftUI & Jetpack Compose components included".	App screens: Yes. "templates for mobile & desktop", such as analytics, checkout, ecommerce, mailbox and task manager.	Look before paying: Yes. A "Preview in Figma" link on its page.
Setproduct Mobile X	iOS and Android: Yes. Its page says "Fits for Android & iOS applications".	Apple and Material components: Not on its page. Its page says "Templates are based on iOS specs adopted for 8dp Android grid" and does not name Material components.	One system for both: Not on its page. One set of templates on iOS specs, adapted to the Android grid. No shared token set or platform switch is named.	Dark as a variable mode: No. Its page says "Dark theme made with Variants" and "Easy to toggle theme for each component": dark is a variant set on each component.	Brand in variables: Not on its page. Its page names no variables or tokens.	Token values for code: Not on its page. No token export is named.	Component code: Not on its page. Its page ships a .fig file ("just simply drag and drop .FIG file onto your Figma app") and names no code.	App screens: Yes. "app layouts to design in Figma", from home and checkout to calendars, settings and sheets.	Look before paying: Yes. A "Preview in Figma" link on its page.
Nucleus UI	iOS and Android: Not on its page. Its page says "From mobile apps to web UI kits for dashboards, e-commerce, and marketing pages" and does not name iOS or Android.	Apple and Material components: Not on its page. Its marketing pages name no Apple or Material components; a changelog entry of July 31, 2023 renames "components that are standard in both material and iOS".	One system for both: Not on its page. No platform switch is named.	Dark as a variable mode: Yes. Its page says "Built-in variables make switching between light and dark mode easy."	Brand in variables: Yes. Its page names variables for "colors, typography, effects styles, spacing, and radius" and says "Update the entire library in an instant!"	Token values for code: Not on its page. No token export is named.	Component code: Not on its page. Its page says the kit "is designed exclusively for Figma" and names no code.	App screens: Yes. Mobile app screens and web UI pages in its Pro plan, fewer in Lite.	Look before paying: Yes. A free version, Nucleus Lite, "with basic components and limited pages and kit".
Untitled UI	iOS and Android: Not on its page. Its page names "website and dashboard examples" and "desktop and mobile page examples", and no iOS or Android component.	Apple and Material components: Not on its page. No Apple or Material components are named.	One system for both: Not on its page. No platform switch is named.	Dark as a variable mode: Yes. Its PRO VARIABLES version: "Variables allow you to switch any component, layout, or page to dark mode with one click!"	Brand in variables: Yes. Its page lists "Figma variables" with "Advanced color, spacing and radius variables."	Token values for code: Yes. Its React library carries the values as CSS variables: "Dark mode styles are managed via design tokens and CSS variables, not hardcoded in components."	Component code: Yes. React components "built with Tailwind CSS and React Aria", sold as Untitled UI React.	App screens: Yes. "Practical + useful website and dashboard examples", desktop and mobile pages.	Look before paying: Yes. A free Figma version: "Try our free version of Untitled UI, with basic styles and components."
AlignUI	iOS and Android: Not on its page. Its pages name no iOS or Android components.	Apple and Material components: Not on its page. No Apple or Material components are named.	One system for both: Not on its page. No platform switch is named.	Dark as a variable mode: Yes. Its 1.0 changelog announces "the integration of the much-anticipated Dark Mode alongside Figma's newly introduced Variable feature", and its FAQ says "You can switch themes with a single click."	Brand in variables: Yes. Its Figma page lists "Tokens & Variables" and "Color Variables", and its FAQ says "The latest update includes Figma Variables integration."	Token values for code: Yes. Its FAQ says "All components and tokens are based on a system" and "The Figma design and the code match 1:1", in its React and Tailwind CSS library.	Component code: Yes. React components, "Built for React" and "Styled with TailwindCSS", sold apart from the Figma file.	App screens: Yes. "Ready-made multi-page user flows for apps" for sectors such as HR, finance, marketing and AI, drawn for the web.	Look before paying: Yes. Its FAQ says "We don't offer a free trial for AlignUI, but you can preview all system features in Figma."

The field

The same rows for every kit.

Where it runs, what it is for, how it does dark mode, what developers get, how it is licensed and when to pick it. Nothing here is ranked.

Figma UI kits for mobile apps, six rows each, checked on October 14, 2026
Kit	Where the app runs	Built for	Light and dark	What developers get	License	Use it when
Appetite UI
Appetite UIThis file	iOS and Android as one system: Apple and Material components on the same tokens, with a Platform mode for the measures that differ.	Apps that ship on iOS, Android or both, drawn at phone widths.	Light and Dark modes on one semantic token set, so a screen switches with the system.	Appetite UI Code ships every component in React Native, with an App Starter, and the core set in SwiftUI, Flutter and Jetpack Compose. The Figma file also exports token values.	Paid once, with lifetime updates. The plans are on the pricing page.	One app ships on iOS and Android, or your brand has to sit on top of the system.
Official kits
Apple's iOS and iPadOS 27 UI kitFigma Community, from Apple	iPhone and iPad apps.	iPhone and iPad design comps and user flows, with the components for all common controls and views.	Not on Apple's page: it lists text styles, color styles and materials and does not say how dark mode switches.	Figma and Sketch files. No code or tokens are stated on its pages.	No price on its pages. Apple's license limits it to mock-ups for Apple's own operating systems.	You ship on iOS only and want Apple's exact components.
Google's Material 3 Design KitFigma Community, from Google	Android apps, with Compose first.	Material 3 styles and components, built to work with the Material Theme Builder plugin.	Light and dark color styles backed by variables, switched with the Material Theme Builder plugin.	Jetpack Compose code snippets in the file, and a code export of the theme from Material Theme Builder.	No price on its page. Licensed under CC BY 4.0.	You ship an Android app on Google's baseline.
Mobile kits
Dynamic Layerdynamiclayer.io	iOS, Android or hybrid apps, built with Figma and Flutter. Its pages name one set of templates and no switch between the platforms.	Components and app templates for Figma and Flutter.	Automatic dark mode, every component in both versions.	Flutter code for the components.	A free plan, then a one-time Personal license for one user or an Agency license for a team.	You build in Flutter and want the components as code.
Setproduct Mobile Xsetproduct.com	iOS and Android from one set of templates, "based on iOS specs adopted for 8dp Android grid". No Material components or platform switch are named.	App templates for Figma.	A dark theme made with variants.	No code named on its page.	Paid once, with an Individual and a Business license.	You want ready app templates in one Figma file.
Web kits
Untitled UIuntitledui.com	Websites and web apps. It names no iOS or Android component.	Modern UI and websites, with website and dashboard examples.	Dark mode variables in its PRO version: "Switch designs to dark mode with one click."	React components, built with React Aria and styled with Tailwind CSS.	A free Figma version, then PRO licenses paid once. The React library is sold apart.	You ship a web app, a dashboard or a marketing site.
AlignUIalignui.com	The web, in React. It names no iOS or Android component.	Web products, with sector templates for AI, HR, finance and sales.	Light and dark themes, switched with one click.	React components styled with Tailwind CSS, sold apart from the Figma file.	Paid once, for one user or for five. The code library is sold apart.	You build a web product in React and Tailwind CSS.

Each cell was read on the kit's own page on October 14, 2026. Counts and ratings are left to each kit's page. Starting prices are in the kit picker below, as each maker's page printed them on October 30, 2026, and Appetite UI's plans are on the pricing page. Appetite UI is ours; every other kit is described in its maker's own words.Appetite UI is a UI kit for iOS and Android apps, in Figma and in code, built like a design system. It comes as a Figma file, as code for React Native, SwiftUI, Flutter and Jetpack Compose, or both, and one token source drives Apple and Material components in light and dark mode.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.

Verdicts

Which Figma UI kit fits your app?

Apple's iOS 27 UI kit for an app that ships on iPhone only, the Material 3 Design Kit for Android only, Untitled UI or AlignUI for the web, Dynamic Layer for Flutter code, Appetite UI when one app ships on iOS and Android. Each line is fair to the other kit and says when this file is the better answer.

iOS only

Apple's iOS and iPadOS 27 UI kit

Use Apple's iOS and iPadOS 27 UI kit if you ship on iOS only and want Apple's exact components. Use Appetite UI if the same app also ships on Android, or your brand has to sit on top of the system.

Read the comparison

Android only

Google's Material 3 Design Kit

Use Google's Material 3 Design Kit if you ship an Android app on Google's baseline. Use Appetite UI if Material roles need to carry your brand and the same app ships on iOS.

Read the comparison

Flutter code

Dynamic Layer

Use Dynamic Layer if you build in Flutter and want the components as code. Use Appetite UI if your developers need the same tokens in SwiftUI, Compose, Flutter or CSS.

Read the comparison

Mobile kits

Setproduct Mobile X

Use Setproduct Mobile X if you want ready app templates in one Figma file. Use Appetite UI if the same screens have to run on tokens you control, in light and dark.

Read the comparison

Web

Untitled UI

Use Untitled UI if you ship a web app, a dashboard or a marketing site. Use Appetite UI if you ship an iOS or Android app.

Read the comparison

Web kits

AlignUI

Use AlignUI if you build a web product in React and Tailwind CSS. Use Appetite UI if the product is an iOS or Android app.

alignui.com

Kit picker

Answer six questions, get a kit.

The kit to start with and two more to look at. Appetite UI comes up for an iOS and Android app, in Figma or in code. It has nothing for the web.

Your answers

An app on iPhone and iPad only: start with Apple's iOS and iPadOS 27 UI kit, then Appetite UI or Dynamic Layer.
An app on Android only: start with Google's Material 3 Design Kit, then Appetite UI or Dynamic Layer.
One app on iOS and Android, with your brand: start with Appetite UI, then Dynamic Layer or Nucleus UI.
A Flutter app with coded components: start with Appetite UI, then Dynamic Layer or Xela UI.
A React Native app with coded components: start with Appetite UI, then gluestack UI or Dynamic Layer.
A web app or a dashboard: start with Untitled UI, then AlignUI or Xela UI.

Before you pick

Answer these before you open a file.

Each answer rules out part of the table, this file included.

Platform

A phone or a browser?

A browser wants a web kit, one phone platform its official kit, and both platforms one file.

See both platforms in one file

Brand

Will the brand change?

If a new brand color takes more than one edit, the file will drift.

See how a rebrand travels

Handoff

Values or a document?

A spec gets retyped, and every retyped value is a place design and build can disagree.

Read the code output

Fit

Where this file is the wrong buy.

Buy something else

When a different file is the better answer.

You are building for the web. A web system will serve you better and cost you less time.
You want a pile of screens to copy from rather than a system to build on.
Your team already runs a mature design system of its own.