Uizard exports pictures of your app, plus React for one component at a time.
There is no app at the end of Uizard. The export dialog offers four file types, JPG, PNG, SVG and PDF, and Uizard's help centre says those are the only file types it is able to provide at this time. One narrow exception exists. In Handoff Mode you can select a single component and copy its CSS or its React code, or download that one component as a file, on a Pro, Business or Enterprise plan. Uizard's own wording for the ceiling is exact: it is currently not possible to export your entire project to HTML, Javascript, or script, and downloading React code for individual components is the only code export it has. Every claim about Uizard here comes from Uizard's own help centre, pricing page and blog, read on 22 October 2026. If you came looking for the design on a phone, the honest starting point is build mobile app without coding.
The second thing to know is who you are dealing with. Uizard announced on 27 May 2024 that it was joining Miro. The product is still live and still sells, and the documentation you would plan a migration against was last touched in 2024. What follows is what the four formats actually give you, what Handoff Mode costs, what has and has not changed since the acquisition, what Apple says about shipping a prototype link, and which parts of a Uizard project are worth carrying into a build.
Start hereThe short version
A design tool that says, in writing, that it is a design tool.
Uizard's FAQ article asks whether you can publish your design as a fully functional website or app. It answers that this is not currently possible on the platform, and that you would therefore not be able to publish to something like the Play Store, App Store or a hosting site. A few lines later it says that while Uizard simplifies the visual design process, it does not encompass full functionality or coding capabilities, and that many users look for a developer to implement logic in their designs as the next step. That article carries the date 25 November 2024.
Read as a product decision rather than a shortcoming, that is reasonable. A clickable mockup that forty colleagues review in a browser is doing a real job, and it does it in an afternoon. The gap only hurts when somebody set a launch date on the assumption that the prototype was most of the app. It was the specification. Everything underneath it, the data, the accounts, the offline behaviour and the store listing, is still ahead of you.
What do you actually get when you export from Uizard?
Image files and a PDF. The flow is short. Select every screen with CMD or CTRL plus A, click Handoff Mode in the right-hand menu, pick a scale of 1x, 2x, 3x or 4x, pick PDF, JPG, SVG or PNG, check the Preview panel, and click Export. PNG has a toggle for a transparent background. You can do the same thing with a selection instead of the whole project, and in that case each screen or component comes out as a separate file. Uizard states the boundary plainly: these are the only file types it is able to provide at this time, and it adds that it is working on expanding the variety of export formats so you can expect more options in the future. The article carrying that sentence is dated 12 June 2024.
Handoff Mode is the one place code appears, and it is narrower than the name suggests. You select a component, open the pane, and switch between CSS and React. There is a Copy code button, and for React a Download component button if you want a file. Uizard repeats twice in the same article that you can only see the code of one component at a time. The feature sits behind a paid plan. On the pricing page read on 22 October 2026, the Free tier is listed at $0 with three AI generations a month and no developer handoff at all. Pro lists developer handoff with React and CSS at $12 a month billed annually, and Business at $39 a month billed annually. Enterprise is quoted by sales.
One detail decides whether any of this helps a phone project. The toggle offers CSS, which is a browser stylesheet language, so the React you copy is a web component. The words React Native, Swift, Kotlin, Xcode, Android Studio, APK and TestFlight appear nowhere in Uizard's export article, its sharing article or its FAQ, checked on 22 October 2026. So the honest use for a Handoff Mode export is as a measurement sheet. It tells you the exact padding, the exact hex values and the type sizes a designer chose, which is worth having and is not the same as a head start on the code.
Uizard Help Center, Exporting projects, dated 12 June 2024, read 22 October 2026
Check yours
What leaves Uizard, and in what shape
Tick what your project contains. The left column is Uizard's own answer from its help centre, read on 22 October 2026. The right column is what that leaves you holding on the day you rebuild.
Nothing ticked. Tick "The project as code" first, because that row is the one people assume wrongly and it changes every estimate that follows.
Who owns Uizard now, and does that change your plan?
Miro does. Uizard announced it itself, on its own blog, on 27 May 2024, in a post titled Uizard joins Miro. The post says the team is joining the Miro family, that for now Uizard will continue to be available and that nothing about the day to day product experience will change. It also gives a bit of history worth knowing before you trust a tool with a quarter of work: Uizard started in 2018, built its first version in Copenhagen, and claimed at the time of the announcement that more than 3 million professionals were using it.
Two things are worth checking yourself, because they are visible from outside and they bear on your plan. The first is the publishing record. The newest post on Uizard's blog is Autodesigner 2.0 is here, dated 12 June 2024, two weeks after the acquisition post, and there is nothing after it as of 22 October 2026. The export article and the sharing article both carry 12 June 2024. The FAQ carries 25 November 2024. The footer of uizard.io reads 2024 Uizard Technologies, and the help centre footer reads 2023.
The second is stranger. Uizard's marketing site does not mention Miro anywhere, not on the homepage, the pricing page, the about page, the press page or the page written for developers, all five checked on 22 October 2026. Search the help centre for Miro and it returns exactly one article, Sharing projects, where Miro is one of five places you can paste an embed code, listed beside Notion, Monday.com, Confluence and Jira. So this is not a sunset notice. The signup and pricing pages are live and the product still sells. It is a tool that kept running while the people writing about it moved on to other things.
What that means in practice is one sentence long. Plan against the 2024 export list, because that is the list, and do not hold a timeline open waiting for a code exporter that nobody has mentioned in over two years. If you want the comparison with a tool that sits closer to the code, the sibling page plasmic to mobile app asks the same questions of a different product and gets different answers.
Uizard Help Center, Exporting projects and its related articles, read 22 October 2026
A published prototype and an installed app, side by side
The left column is what Uizard documents today. Publish a project, copy the link or the embed code, and share it. The right column is what an installed build does. Read it as a list of jobs rather than a scoreboard, because for design review the left column wins on effort by a mile.
| The job | A published Uizard prototype | An app you build and ship |
|---|---|---|
| Opens at a URL in any browser | Yes | No |
| Embeddable in Notion, Miro, Monday.com or your own site | Yes, with the embed code from the Share menu | No |
| Taps move you between screens | Yes, in the published prototype | Yes |
| Reads or writes real data | No | Yes |
| Listed on the App Store or Google Play | No | Yes |
| Sits as an icon on the home screen | No | Yes |
| Works with no signal | No | Yes |
| Goes through App Review | No | Yes |
| Who owns the output | You do. Uizard says it takes no ownership of what users create | You do, including the source code |
Can you wrap the published prototype link and ship that?
People try, so here is what Apple has written. Guideline 4.2 says your app should include features, content and UI that elevate it beyond a repackaged website, and that an app which is not particularly useful, unique or app-like does not belong on the App Store. Guideline 4.2.2 says that other than catalogs, apps should not primarily be marketing materials, advertisements, web clippings, content aggregators or a collection of links. A build whose only screen loads your prototype URL is the thing those two sentences describe.
There is a worse problem than the guideline, though, and it is specific to a design tool. Behind a Uizard prototype there is nothing. Uizard's FAQ says there is no way to integrate or connect a database or store data, and that API access is not available. So a reviewer tapping through your wrapper finds buttons that go to the next picture and a form that forgets what was typed into it. Guideline 2.1 asks for final versions with placeholder text and other temporary content scrubbed before submission. A prototype is placeholder content by definition.
The same mistake has a quieter version that costs people a week. Those 4x PNG exports look exactly like store screenshots, and they are not allowed to be. Guideline 2.3.3 says screenshots should show the app in use, and not merely the title art, login page or splash screen. Guideline 2.3.4 is stricter about video: previews may only use video screen captures of the app itself. Build the screens, run them on a device, then capture them. Your Uizard files are the plan for those screenshots and not the screenshots.
Apple, App Store Review Guidelines, last updated 16 October 2026, read 22 October 2026
What carries over if you rebuild the designs as a real app?
The decisions do, and that is most of the value. You know how many screens there are, what each one is called, what the user taps to get to the next one, which words are on the buttons and what the thing looks like. Getting a team to agree on that list is usually the slowest part of a project, and you have already done it. Your ownership is not in question either: Uizard's FAQ says all content, prompts and information belong solely to the users, that it takes no ownership of intellectual property created by users, and that you are free to use your projects as you like.
One practical tip about the handover, learned the hard way. Export screens individually rather than dumping the whole project into one PDF. Uizard supports this directly: select the screens you want, open Handoff Mode, and each one comes out as its own file. Anyone matching a design, a person or an AI builder, does better with one clean image per screen than with a sheet of thumbnails, because there is no guessing about which rectangle is the screen. Keep your Uizard screen names on the files, so the names travel with the pictures.
Newly is one way to do the build. You describe the app in plain English, hand over the exported screens one at a time, and it writes a real React Native and Expo project that you own, with two-way GitHub sync so the code is never anywhere you cannot reach. It uploads iOS builds to TestFlight, publishes to Google Play internal testing, and builds a standalone Android APK. It is $25 a month, with no free tier. What it will not do is press submit on the App Store for you, and that is on purpose. Apple's guideline 4.2.6 says apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app's content, and that such services should not submit on behalf of their clients. The account and the submission stay yours, and the steps are in publish to app store.
A closing word on when to stay put. If the prototype exists so that a client can click through it and sign off, Uizard is already the right tool and an installed build adds a review queue for nothing. Rebuild when you need the icon on a home screen, the thing to work in a basement with no signal, a notification to arrive without anyone opening a browser, or real records to be saved. None of those four are design problems, which is why none of them were ever going to come out of a design tool. For the same decision taken from a web design starting point, see relume to mobile app.
Apple, App Store Review Guidelines, guidelines 2.1, 2.3.3 and 4.2.6, read 22 October 2026
Questions people ask about Uizard and mobile apps
For one component at a time, and only on a paid plan. Uizard's Handoff Mode lets you select a single component and copy its CSS or its React code, or press Download component for a file version, and the help centre notes that this is available to users with Pro, Business or Enterprise subscriptions. The limit is written down in the same article: it is currently not possible to export your entire Uizard project to HTML, Javascript, or script, and downloading React code for individual components is the only code export Uizard has. Read on 22 October 2026.
The design is done. Describe what it has to do.
Export your screens one at a time at 2x. Write down what each screen saves, who is allowed to see it, and the one thing it has to do with no signal. That list, plus the pictures, is the whole brief for the app.
Start building