Contents
App recreator — in developmentScope: what a recreated app is and isn'tHow you'll use itCopying an app is a bad idea; learning its flow is notWho asked for thisFrequently asked questionsEvery product team starts the same way: "build me something like that app, but for our market." Today that means a designer redrawing screenshots for a week. Recreating an app compresses it — paste the store link, get the screen inventory, the navigation map, the design tokens and a clickable prototype to argue about on day one.
This is the most ambitious tool in the /make family and it is in development. Here is the plan, the limits, and what Rekreate can do for your app today.
- Input: an App Store or Google Play link (or your own screenshots).
- Output: screen inventory, navigation flow, design tokens, clickable prototype.
- It recreates the interface and flow, never the code, data or business logic behind it.
- In development. App marketing videos are something we can make today.
App recreator — in development
Paste a store link. Rekreate pulls the public listing — screenshots, category, description — reconstructs the screen inventory and the navigation between screens, extracts a design system (palette, type scale, components) and assembles a clickable prototype of the main flow: onboarding, home, detail, settings, paywall.
From there you rebrand it, cut what you don't need, and hand your team a starting point instead of a blank Figma file.
This tool is not live yet. Create a free account and we will let you know in the app as soon as it opens.
What you can do today
What Rekreate can already do around an app:
- Recreate video ads — the UGC ads that install apps, rebuilt with your product.
- Recreate a photo — store screenshots and feature graphics in your brand.
- Recreate a logo — a clean app icon and brand assets.
All of them are live; the prototype builder is the piece still being built.
Scope: what a recreated app is and isn't
| Planned | |
|---|---|
| Screen inventory | Yes — every screen visible in public listings and any screenshots you add |
| Navigation map | Yes — tabs, stacks, modals and the main user path |
| Design tokens and components | Yes — palette, type, spacing, buttons, cards, lists, forms |
| Clickable prototype | Yes — enough to test the flow with users and stakeholders |
| Production code | Later — the first release targets prototype and design output |
| Their back end, algorithms, data | Never — none of that is visible from a store listing and none of it is yours to take |
How you'll use it
Paste the store link
App Store or Google Play. Add your own screenshots for screens that are behind a login.
Review the flow
Check the reconstructed navigation: what is a tab, what is a modal, where the paywall sits.
Rebrand it
Swap palette, type and icon for yours, then cut the screens your version does not need.
Hand it to the team
Export the prototype for user testing and the tokens for the engineers — the argument now happens over something real.
Copying an app is a bad idea; learning its flow is not
Interface conventions — a tab bar, an onboarding carousel, a paywall after the third action — are industry practice, and recreating them is how every product team works.
What you cannot take: the app's name, logo, icon, custom illustrations, copy, trademarks, and anything proprietary under the surface. Cloning an app closely enough to confuse users is both a trademark problem and a fast route to store rejection: both Apple and Google remove apps that duplicate an existing one.
Use a recreation to understand structure and to skip the blank page. Then change enough that your app is obviously its own product — which is also the only version that has a reason to exist.
Who asked for this
- Founders validating "this app, but for our niche or country" before hiring anyone.
- Agencies turning a client's reference app into a prototype during the pitch.
- Product teams documenting a competitor's flow properly instead of passing screenshots around Slack.
- Designers who want the structure in front of them so the first design review is about decisions, not layout archaeology.
Create a free Rekreate account to get it in the app when it opens — and use the live free tools in the meantime.
Frequently asked questions
Can AI recreate a mobile app from a store link?
It can reconstruct the public interface: screens, navigation and design system, and assemble a clickable prototype. It cannot recover the app's source code, back end or data — none of that is public.
Will I get working code for iOS and Android?
The first release targets prototype and design output — screens, flows and tokens. Code generation is the step after that.
Is it legal to recreate an app?
Learning from an app's structure is standard product practice. Copying its name, icon, artwork, copy or proprietary code is not, and near-clones get removed from both app stores.
What about screens behind a login?
They are not in public listings. Add your own screenshots of the flows you have access to and the tool includes them.
When will the app recreator be available?
It is in development with no public date. Create a free account and new tools appear in the app as they open.
What can Rekreate do for my app today?
Produce the marketing around it — UGC-style video ads, store screenshots and brand assets. See the free tools.
Create your next viral video with Rekreate
Find a proven short-form video, recreate it with your script, avatar and voice, and generate scenes with Seedance, Kling and Veo in one workspace.
Start free trial →