App templates promise the same thing on every marketplace: skip months of work and start from something that already runs. Sometimes that is true. Often you get a set of screenshots, or a project that stopped building two SDK versions ago. This buyer guide to mobile app templates is about choosing the right kind of template for your plan, reading a listing like a developer, and checking a purchase while you can still ask questions. It covers Flutter, React Native and native Android templates. Shelf numbers were measured on the Getly catalogue on 29 October 2026.
If you only care about native Android projects and want to know what a source ZIP should contain file by file, we have a separate deep dive: Android app templates: what's inside the source ZIP. This article is the wider question that comes first: which template, on which stack, for which job.
Three products hide behind the words "app template"
| Type | What you get | Good for |
|---|---|---|
| UI design kit | Screens as images, Figma or PDF | Showing a client or a designer the look you want |
| UI code kit | Working screens in code, mock data, no backend | Saving front-end time on an app you will wire up yourself |
| Full app | Screens, logic, storage or backend, build instructions | Launching quickly, learning a real project end to end |
All three are honest products at their own price. Problems start when a buyer expects the third and receives the first. The listing title rarely tells you which one it is, so look at the file list and the words "source code", "run with", "Flutter SDK", "Android Studio".
What the shelf looks like right now
We measured the mobile categories together: Android App Templates, Mobile Apps, the Flutter, React Native and iOS template categories and Mobile App Templates. They hold 198 active listings. The middle half costs between $2.99 and $28.60, the median is $6.90, and 2% are free.
The file mix is the important part. 35% of listings deliver only image files, 21% a PDF, and only 25% include an archive at all, the place where code usually lives. 4% ship an APK you can install. In other words, roughly a third of what sits on these shelves is design, not software. The iOS and React Native categories hold only a handful of listings, and most of them are not app projects, so for working code today Flutter and native Android are where to look.
Licences are mostly unstated: 79% of listings set no licence type, 11% are personal use, and about 10% allow commercial, extended or CC0 use. Publishing an app built from a template is commercial use, so this is a question to settle before paying.
Picking a stack: what to ask for each
Flutter
One codebase for Android and iOS, and most of the real code on our shelf. Ask for the Flutter and Dart SDK versions (they live in pubspec.yaml), whether the project uses Material 3, and which state management it uses. A good listing tells you the exact commands to run: flutter pub get and flutter run.
React Native
Ask whether the project uses Expo or bare React Native, which Expo SDK or React Native version, and whether it is TypeScript. An Expo project several SDK versions behind usually means an upgrade job before your first build. Check package.json in the file list or ask for a screenshot of it.
Native Android
Kotlin or Java, Jetpack Compose or XML layouts, and the target SDK. For Google Play this matters: Google's developer documentation, checked on 29 October 2026, requires new apps and updates to target Android 16 (API level 36) from 31 August 2026. A project targeting an older SDK will need work before publishing.
Whatever the stack, remember that building for iOS needs a Mac with Xcode and an Apple developer account. A "cross-platform" template does not remove that requirement.
Six checks before you pay
- Source or screens. The listing should say "source code" and show an archive in the file list. A few megabytes of ZIP with a README is a project; a single PNG is a picture.
- Versions in numbers. "Flutter 3.19+" or "Expo SDK 51" is a promise you can check. "Latest version" is not.
- What is mocked. UI code kits use fake data. That is fine, as long as the listing says it. Login screens without a real auth backend are common.
- Screen count and a list. Good sellers name every screen. Compare the list with the previews.
- Commercial licence. If you will publish, the listing must allow commercial use, or the seller must confirm it in a message.
- A demo. Sellers on Getly can attach a free demo download or trial link next to the price. An APK you can install on a spare phone is the fastest proof that the app runs.
Listings on Getly worth opening
Chosen because the description lists the stack, the screens and the files, so you can judge before buying.
- Flutter Budget & Expense Tracker App Template, $3.99, commercial licence. Flutter 3 and Material 3 source with six screens plus an add sheet, eight languages including Russian and right-to-left Arabic and Hebrew, charts and per-locale currency formatting. A full small app rather than a design.
- GlassTask UI, Flutter Task Manager Template, $14.99, commercial licence. Five screens with reusable glassmorphism widgets, splash animation, README and licence file. A UI code kit for a productivity app.
- Aether Finance, Fintech Flutter UI Kit, $25. Seventeen-plus finance screens on a bento grid layout: dashboard, transaction timeline, card vault and more. A larger UI code kit for wallets and finance trackers.
- Gym Store, Flutter E-Commerce UI Kit, $49, commercial licence. Nineteen screens covering onboarding, authentication with OTP, catalogue, cart, order tracking and profile, light and dark mode, Flutter SDK 3.19+ stated.
- TradeLog, Android Trading Journal, $14.99, commercial licence. Native Android in Java and XML: an installable APK, the full Android Studio project, README with build steps and a licence file.
After you buy: the first evening
Open the project on a clean machine the same day. Run the install and build commands, note every error, and walk through every screen from the description on a real device. Search the project for API keys and Firebase config files: you will replace them all with your own, and the author's live keys left inside tell you something about the care that went into the project. If something promised is missing, write to the seller first, and if that does not resolve it, request a refund within the store's refund window (at least 30 days), which Getly staff review.
Paying on Getly
Cards (Visa, Mastercard) and USDT/USDC stablecoins are accepted. Files stay in your library after purchase, so you can download a later version again. The developer keeps 80-90% of the price, which is how small independent template authors keep updating their projects.



