A Flutter UI kit is a set of ready screens and widgets in Dart; a Flutter app template goes further and adds working logic, navigation and often a backend. Before you pay for either, check five things in the source: the Flutter and Dart versions it builds on, the state management it uses, which backend it expects, whether it is screens only or a working app, and what the licence lets you ship. This guide walks through those checks by app type, with what such kits cost on Getly today.
What the shelf looks like today
We measured Getly on 4 November 2026. Two sets of numbers, describing different things:
- Flutter listings. Listings with "flutter" in the name: 18. These are mostly full source projects, and the prices show it. The middle half costs between $31.24 and $210, with a median of $95. None is free. 88.9% state no licence, and 11.1% carry a commercial one.
- The whole shelf. Android app templates, mobile apps and software together: 493 listings, median $14.90, middle half $5 to $44.98, 2% free. Here 55.6% of listings state no licence, 20.1% a commercial one and 20.3% a personal one. This shelf mixes app templates in many stacks with tools, plugins and licence keys.
The licence number is the one to remember. Almost nine in ten Flutter listings do not say what you may do with the code. For source code that you plan to ship in a store under your own name, that is a question to ask before paying, every time.
UI kit or full app template
| UI kit | App template | |
|---|---|---|
| What you get | Screens, widgets, theme, sample data | Screens plus navigation, state, API calls, often an admin panel |
| Backend | None, data is hard-coded | Firebase, Supabase, a REST API or the seller's own server code |
| Work left for you | All logic, data, auth, payments | Configuration, branding, your content, store publishing |
| Typical risk | Screens that look finished but hide nothing behind them | Outdated packages and a backend you must host and maintain |
Read the description for words like "fully functional", "with backend", "admin panel" or "UI only". If the listing does not say, assume it is UI only.
The source checks before you pay
Flutter and Dart versions
Ask for, or look for in the screenshots, the pubspec.yaml file. The environment: sdk: line tells you the Dart version. A project below Dart 3 predates the current language and may need real migration work. Check the date of the last update in the description too: Flutter moves fast, and a kit untouched for two years will show deprecation warnings on the first build.
Dependencies
The dependencies: block in pubspec.yaml lists every package. Look for three things: very old version pins, packages that are discontinued, and many packages for small jobs. Each one is a future upgrade. A kit with a short, current dependency list ages better.
State management
Provider, Riverpod, Bloc and GetX all work, but they are not interchangeable. If your team already uses one, buy a kit built on it. Switching state management in a finished app costs more than the kit.
Structure
Look for a folder structure that separates screens, widgets, models and services. One giant main.dart or screens with API calls inside build methods means you will rewrite it to add features.
Platforms
Flutter can target Android, iOS, web and desktop, but a kit is tested on what the seller says. If you need iOS, check that the listing mentions it and that the project contains an ios folder with a set-up guide.
A demo you can run
The best proof is a demo APK, a web build or a video of the app being used, not only screenshots. Screenshots show design; a demo shows that navigation, forms and loading states work.
Documentation
You want a guide that covers renaming the package, changing the app icon and splash screen, setting your API keys or Firebase project and building a release. Without it, the first day goes on guesswork.
Assets
Fonts, illustrations, icons and photos in the kit have their own licences. Check that the kit says they are included for commercial use, or plan to replace them.
By app type: what to look for
| App type | Screens it must have | Extra check |
|---|---|---|
| E-commerce | Catalogue, product, cart, checkout, orders, profile | Which payment SDK, if any, and whether stock and orders come from a real backend |
| Food or grocery delivery | Restaurants or stores, menu, cart, order tracking | Separate apps for courier and store, maps package and its API key |
| Taxi or transport | Map, pickup and drop-off, ride status, driver view | Live location updates and which maps provider it needs |
| Travel booking | Search, results, detail, booking, trips | Date pickers and whether prices come from an API or sample data |
| Chat or social | Conversations, chat, profile, notifications | Real-time backend and push notification set-up |
| Fitness or health | Plans, workout, progress charts | Charts package and whether data is stored locally or online |
| Finance or wallet | Balance, transactions, cards, transfers | Security of stored data; treat it as UI only until proven otherwise |
On Getly you can look at the Gradient Transport App Template ($7) and the Gradient Travel App Template New UI ($5), two app templates for the transport and travel types above. Their names do not say which framework they use, so read the description and file list for the stack before you buy, and run the same checks.
Licences for source code
With app source code, the licence decides what you can ship. These are the questions to settle, in writing on the product page or in a message to the seller:
- May you publish an app built on it in the stores under your own name?
- One app or several? Many code licences cover a single end product.
- May you build it for a client who then owns the app?
- May you charge users, or show ads, in the app?
- What is never allowed: reselling or sharing the source itself, as is or lightly changed.
Since most Flutter listings we measured state no licence, ask first. A short written answer from the seller is worth keeping with your purchase.
After you download
- Run
flutter pub getandflutter analyze. Count the warnings. - Build and run on a real device, not only the emulator.
- Rename the package and app ID before you write any code of your own.
- Replace sample keys and endpoints with yours. Never ship the seller's test keys.
- Commit the original to version control, so you can always compare with what you bought.
Buying on Getly
You can pay by card, with Apple Pay or Google Pay where your device supports it, or with USDT/USDC stablecoins. PayPal is not accepted. You do not need an account. Card orders deliver the files right after payment, and the receipt email has a download link for each file. Each store sets a refund window of at least 30 days. More app templates are on the Android app templates and mobile apps shelves.



