Skip to content

Comparison

Android only, or both in 2026? The file follows.

Use the Material 3 kit for an Android app on Google's baseline. Use Appetite UI when Material roles need to carry your brand and the same app ships on iOS.Checked on against Figma CommunityAppetite 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.

An Appetite UI tile beside a tile with a Material 3 checkbox, standing for Google's Material 3 Design Kit, over a soft coastal landscape

Verdict

The platforms you ship pick the file.

Use the Material 3 kit if

  • You ship an Android app on Google's baseline.

    In its own words, an introduction to Material Design 3 with styles and components, built to work with the Material Theme Builder plugin.

Use Appetite UI if

  • Material roles need to carry your brand and the same app ships on iOS.

    brand/base is one color that the Material primary role and the iOS tint both resolve to, and Native mode returns each platform to its published value.

Use both when Google's kit is your reference for the Android baseline.

Side by side

The same rows for both files.

Google's column is what its pages say, read on its Figma Community page and the Material 3 pages.

Appetite UI and the Material 3 kit compared row by row, checked on October 14, 2026
CriterionAppetite UIThis fileGoogle's Material 3 Design KitFigma Community
What it isA UI kit for iOS and Android apps, in Figma and in code, built like a design system.An introduction to Material Design 3, with styles and components to help you get started, built to work with the Material Theme Builder plugin.
Built foriOS and Android apps, drawn at phone widths.Android apps, built for Jetpack Compose.
iOS and Android conventionsApple and Material components in one file, with 15 Apple system colors and 32 Material 3 roles, each pointing at a token you control.Material 3 on Android. Its page describes no iOS version.
Light and darkLight and Dark modes on one semantic token set, so a screen switches with the system.Light and dark color styles backed by variables, switched with the Material Theme Builder plugin.
A new brand colorOne edit. Both platforms and both modes follow it.Material Theme Builder: "Colors will be shifted to generate accessible colors within the same color space as dynamic colors."
What developers getAppetite 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.Jetpack Compose code snippets in the file, and a code export of the theme from Material Theme Builder.
LicensePaid once, with lifetime updates. The plans are on the pricing page.No price on its page. Licensed under CC BY 4.0.
Use it ifMaterial roles need to carry your brand and the same app ships on iOS.You ship an Android app on Google's baseline.

Checked on . Google's kit page states no price and licenses the file under CC BY 4.0. Counts and ratings are left to its page.

Two platforms

Which Figma UI kit works for an app on both iOS and Android?

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 599 variables, and its Platform Bridge opens in Brand mode, with a Native mode that returns each screen to the values Apple and Google publish.

The iOS tab bar and the Material 3 navigation bar from Appetite UI, the same four destinations drawn to each platform's convention

iOS

The same screen on iOS

Switch the Platform mode to ios-lg and the screen takes 44 point targets, a 44 point top bar and 8 point corners.

See the iOS mirror

The brand/base variable in the Color Tokens collection set to orange in one edit, colors/orange/500 in Light and colors/orange/400 in Dark

Brand

One variable, not a generated theme

The Material primary role resolves to brand/base as you set it, and Native mode returns the published value.

See how a rebrand travels

One variable, brand/base, and the name it carries in code: var(--ap-brand-base) in CSS, Color.apBrandBase in SwiftUI, AppetiteTheme.colors.brandBase in Jetpack Compose and apBrandBase in Flutter

Handoff

The same name in four codebases

One variable arrives as a CSS property, a SwiftUI color, a Compose theme value and a Flutter constant.

Read the code output

Judge it on your own screens.

A table only goes so far. The preview shows how the kit behaves on a screen of yours.