Relume exports real code, and all of it is for a browser.
Relume is usually filed as a wireframe tool that stops at a picture, and that is the wrong way to be wrong about it. Its own React documentation describes the Relume Library for React as a React and Tailwind component library, written in TypeScript, with UI elements based on Shadcn UI. You can run what comes out. It renders HTML in a browser, and the product has no other target. Across Relume's homepage, its Export product page, its pricing page and its React library documentation, read on 22 October 2026, the phrases React Native, iOS, Android, app store and mobile app appear zero times in the visible text. There is no app export because there is nothing to export to. If the thing you want at the end is an app on a phone, start at build mobile app without coding.
What follows is what Relume documents itself as producing, what the React export quietly leaves behind, why React and React Native are not interchangeable, what Apple says about shipping a wrapped marketing site, and which half of a Relume project is worth carrying into a phone build. That last one is the useful part, and it is bigger than people expect.
Start hereThe short version
The deliverable is a website, and the sitemap is what travels.
Relume's homepage puts the product in one line: start with a brief, and Relume builds the sitemap, the wireframes and a marketing site you would actually publish. Its Export page spells the pipeline out as three steps. A sitemap that scopes every page before anything is designed. Wireframes built from real components, with copy included. A style guide that sets colours, type and spacing once and applies them across every page. Then you export the lot, into Figma, Webflow, React or plain HTML, or you hand the library to an AI editor through the Relume Library MCP.
So the migration question is not how to convert a Relume project. It is which half of the work transfers. The first two steps of that pipeline transfer completely, because a sitemap and a set of written sections are platform-agnostic by nature. The wireframes do not, because a marketing page and an app screen are different objects with different jobs. Plan for that split and Relume is a genuinely good place to have started. Plan for an export button and you will spend a week looking for one.
What does Relume actually produce?
Four export paths and a library connector, and the Export page is direct about it: one system, four ways to design and export. Figma gives you the whole project as a Figma file with the style guide included. Webflow takes the project in with classes and structure intact, which Relume's homepage describes as clean client-first classes ready with no cleanup. React gives you production-ready React with Tailwind CSS and Shadcn UI, or plain HTML, to drop into your codebase. The Library MCP connects the same components to Cursor, Claude and other AI editors.
One phrase on that page is worth reading slowly, because it is the reason a lot of people land here. Relume describes more than 1,000 responsive components with mobile variants, and describes the Figma path as arriving with mobile variants and style guide included. A mobile variant is how the same web page lays itself out in a narrow window. It is a breakpoint. Nothing about it is an application binary, and no step after it turns one into the other.
The engine behind all of this is also documented, under the heading assembled, not generated: the AI does not write raw code, it selects from components Relume's own designers build and maintain, then assembles them into your site. Relume puts the component system behind 2 million websites. That design decision is why the output is consistent, and it is also why a mobile target is not a small feature away. A phone export would need a second library of native components, built and maintained by the same team, for a different renderer.
Relume, Relume React Docs, intro and element reference, read 22 October 2026
Check yours
Where each Relume export path actually ends
Tick the export you were planning to use. The left column is Relume's own description of that path, from its Export product page and its React library documentation, both read on 22 October 2026. The right column is what the path means if the thing you want at the end is an app on a phone.
Nothing ticked yet. All five paths end at something a browser renders, so the choice between them changes how much of your design work you keep, not whether you finish with an app.
The MCP row is the one that tempts people with an agent to hand. A connector that lets Cursor or Claude build with real components instead of guessing at markup is a real improvement over guessing, and the components on the other end of it are still web components. What an AI agent is good for depends entirely on which platform you point it at, which is the thread running through devin to mobile app.
Is the Relume React export a React Native project?
No, and the overlap in the names has cost people real time. Relume documents its React library as React, TypeScript and Tailwind CSS, with UI elements based on Shadcn UI, and says the components are fully typed with props so you can copy the source of any section straight out of the library and keep full control over the markup and the CSS. Every word of that describes a DOM. Tailwind compiles to CSS rules that apply to HTML elements. Shadcn UI is a set of browser components. React Native renders platform views instead, so a class name string and a div have nothing to attach to once you get there.
The element list in the same documentation settles it without any argument from us. Relume ships twenty UI elements: Accordion, Badge, Breadcrumb, Button, Carousel, Checkbox, Dialog, Dropdown Menu, Input, Label, Pagination, RadioGroup, Select, Separator, Sheet, Sidebar, Switch, Tabs, Textarea and Tooltip. A breadcrumb trail, a pagination strip, a sidebar and a hover tooltip are things that exist because a page is wide and a mouse has a cursor. The component categories in Relume's own sitemap, 50 of them when we counted on 22 October 2026, go further in the same direction: cookie consent banners, navbars, footers, topbars and application shells.
There is a second thing the React path leaves out, and Relume flags it itself rather than letting you discover it. The documentation carries a warning that exporting the Relume Style Guide or Relume Designs is not supported with the React export, that you will only be exporting unstyled wireframes, which it glosses as layouts, from the Site Builder, and that there is no ETA on when the feature will be released. The practical effect is that the Figma and Webflow paths carry your brand and the React path carries your structure. If you were counting on the React export to hand a developer something that already looked like your brand, that is the sentence to read before you promise it to anyone. A builder whose output genuinely is an installable Android package behaves differently from the inside, which is the subject of mit app inventor to mobile app.
Relume, Relume React Docs, React export warning and element list, read 22 October 2026
Can you wrap a Relume site in an app and ship it?
This is the shortcut everybody reaches for once the export answer sinks in, so it is worth knowing what Apple has written down. 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 is narrower and lands closer to a Relume project: other than catalogs, apps should not primarily be marketing materials, advertisements, web clippings, content aggregators or a collection of links.
Read those two sentences next to Relume's own description of what it builds, which is a marketing site. A web view pointed at a marketing site is the single clearest example of the thing 4.2.2 names. The guideline does not ban web views, and plenty of shipped apps contain them, so the test is about the app as a whole and whether there is enough of it to justify an install. A reviewer working through a queue can tell the difference in well under a minute.
The wrapper also disappoints people on the occasions it does pass, for reasons that have nothing to do with review. A page loaded over the network needs the network. It holds no state when the connection drops in a lift, it cannot wake the phone with a notification, and every reason anyone wanted the app in the first place tends to live in exactly those gaps. If the honest answer is that a good responsive website does the job, Relume Publish will host it for you and the whole question goes away.
A Relume site and an installed app, job by job
The left column is what Relume documents today, including what its hosting product does and what the React export leaves out. The right column is an installed build. Read it as a list of jobs rather than a scoreboard, because for a brochure site, a launch page or a client handover the left column wins on effort and nothing else matters.
| The job | A Relume project | An app you build and ship |
|---|---|---|
| Opens at a URL in any browser | Yes | No |
| Hosted for you without setting up a server | Yes, through Relume Publish, free on a relume.live subdomain | No |
| Arrives carrying your Relume style guide | Figma and Webflow yes, React export no | Only what you rebuild |
| Listed on the App Store or Google Play | No | Yes |
| Sits as an icon on the home screen | No | Yes |
| Still works when the signal drops | No | Yes, for whatever you store on the device |
| Can send a push notification | No | Yes |
| Reads the camera or a barcode | Only through browser permissions | Yes |
| Goes through App Review | No | Yes |
What carries over if you rebuild it for a phone?
More than you think, and none of it is markup. Your sitemap is the valuable artefact, because it already says what screens exist and how they relate to each other. Your copy is written and argued over. Your colours, type and spacing are decided and written down in the style guide. Any competent app build starts by asking for exactly those things, and you have them in a form you can read out loud. A brief that took a week is worth more to the next tool than an export file would be.
The layout is what you leave behind, and it helps to be blunt about why. A marketing page is a long scroll written to persuade a stranger who arrived from a search result, so it restates the offer on the way down and finishes on a call to action. An app screen is a small surface that a signed-in person opens several times a day, so it shows state and then gets out of the way. Those are different design work with different success conditions. Trying to convert one into the other is how a project ends up with a phone app that feels like a pamphlet.
Newly is an AI app builder for the second half of that job. You describe the app in plain English and it writes a real React Native and Expo project you own, with two-way GitHub sync so the code is never somewhere 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 deliberate: Apple guideline 4.2.6 says apps created from a commercialized template or app generation service are rejected unless submitted directly by the provider of the app's content, and adds that such services should not submit on behalf of their clients. The steps you take on that last mile are in publish to app store.
One recommendation to close on. Do not build an app because the website is finished. Relume is built for marketing sites and it is good at them, and a sitemap, a style guide and a hosted site is a complete answer to a great many briefs. Build the app when you need the icon on a home screen, the thing to keep working with no signal, or a notification to arrive without anyone opening a browser. Those are the jobs a URL cannot do, and if none of them is on your list then the honest move is to publish the site and get on with something else.
Questions people ask about taking a Relume project to a mobile app
No. Relume documents four export paths, Figma, Webflow, React and plain HTML, plus a library MCP for AI editors, and every one of them finishes at something a browser renders. There is no build step, no signing step and no store upload anywhere in the product. Across Relume's homepage, its Export product page, its pricing page and its React library documentation, read on 22 October 2026, the phrases React Native, iOS, Android, app store, mobile app and native app appear zero times in the visible text of any of them.
Keep the sitemap. Describe the screens.
Open your Relume sitemap and cross off every page that exists to persuade someone who has not signed up yet. What is left is the app, and that list plus your style guide is the whole brief.
Start building