Plasmic generates React for the web, so the phone app is a second build and not an export.

What does Plasmic actually generate?

Two things, and Plasmic is clear about which one it wants you to use. The first is the Headless API, which it calls the main way to integrate Plasmic into a codebase. No Plasmic code is checked into your repository. You add a little setup, drop a PlasmicComponent into your app where published content should appear, and your editors publish from Studio. On frameworks that support server rendering or static generation, where Plasmic names Next.js and Gatsby, you can make the fetch happen on the server or at build time. For sites that render in the browser, the content comes down from a CDN at runtime.

The second is codegen, which the docs describe as more advanced and recommend against unless you have a reason. You install the Plasmic CLI, run plasmic auth, then plasmic sync with your project ID, and the documentation says plainly what lands: React components for each component in your Plasmic project. The first sync asks what flavour of codegen you want and writes the answers into plasmic.json, with a plasmic.lock beside it. From there it is ordinary code in your repository, reviewed and deployed the way you deploy anything else.

There is a third door for environments Plasmic has no SDK for. The Render API renders any page or component and returns plain HTML, with hydration switched on or off by a query parameter, and the docs say you can render it anywhere you can make a REST API call. Read that sentence carefully before you build a plan on it. Anywhere means anywhere that can display HTML, which on a phone means a web view and nothing else.

Plasmic docs, Technical Overview, read 22 October 2026

Is React Native a documented Plasmic target?

It is not. Eight pages were read for this section on 22 October 2026: the learn index, the introduction, the FAQ, the Developer Quickstart, the plain React quickstart, the technical overview, the Headless API against codegen comparison and the codegen overview. The phrase React Native appears zero times in all eight. So do iOS, Android and Expo. The word mobile appears twice, in a Studio question about building a page with differences on mobile against desktop, which is a breakpoint and not a platform.

Nothing about that is a complaint. Plasmic is doing the thing it says it does, and doing it in a way that explains why a phone target would be a different product rather than a checkbox. The Figma plugin translates a vector document into DOM and CSS. The Render API hands back HTML. A phone screen has neither. Open Expo's own Build a screen tutorial, last modified 22 October 2026, and the imports are View, Text, Pressable and StyleSheet from react-native, with the styles declared as a JavaScript object. There is no div in it and no stylesheet file, so there is nowhere for Plasmic's output to land.

The technical overview ends with the sentence that settles it. After listing the Headless API, codegen and the rest, Plasmic invites you to tell them if you want to see Plasmic integrated into other environments. That is an open door and not a feature. If somebody tells you Plasmic exports a phone app, ask them which documentation page says so, because as of 22 October 2026 there is not one.

Plasmic docs, Technical Overview, other methods of integration, read 22 October 2026

Is Plasmic still being worked on?

Yes, and the answer matters more than it looks, because several tools in this category have shut down or gone quiet and the advice for a dying tool is different. The docs carry a Plasmic MCP page explaining how an AI agent opens your project in Studio through the browser and edits it with Plasmic's own in-page tools API. That page says Plasmic MCP is at an early stage and that the team is actively improving the experience, and it names Claude Code, Codex, Cursor and VS Code Copilot among the clients it works with. A team in maintenance mode does not write that page.

The rest of the site reads the same way. The footer says Plasmic, Inc. with a 2026 copyright. The homepage describes an open-source visual editing and content platform for building websites and apps, offers a free plan with no credit card, and lists comparison pages against tools that are themselves recent. Every one of those is a first party signal, read on 22 October 2026, and none of them is a promise about next year.

So the plan is addition, not replacement. Keep Plasmic where it works, which is the marketing site, the landing pages, the customer portal in your web app, and the arrangement where somebody in marketing publishes without opening a pull request. Build the phone app as its own project against the same data. The same reasoning applies to any visual tool with a web output, which is why relume to mobile app reaches the same conclusion from a different starting point.

Can you ship your Plasmic site inside a web view?

This is the first idea everybody has, and it is worth reading what Apple has written about it before you spend a week on it. Guideline 4.2 says an 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 apart from catalogs, apps should not primarily be marketing materials, advertisements, web clippings, content aggregators or a collection of links. A build whose only screen is your Plasmic URL in a frame is what those two sentences describe.

Note what the guidelines do not say. Web views are allowed and plenty of shipped apps contain them. The test is about the app as a whole, whether there is enough of it to be worth installing. A real screen, a list that still works in a basement, a notification when something changes: those count toward the test, and a reviewer can tell the difference in a minute.

The practical disappointment is worse than the review risk. A page loaded over the network needs the network. It holds no state when the signal drops halfway through a form. It cannot wake the phone up when a record changes. Most of the reasons anyone wanted an app in the first place sit precisely in those gaps, which is why the web view usually gets built, shipped and then quietly replaced within a year.

Apple, App Store Review Guidelines, guidelines 4.2 and 4.2.2, last updated 16 October 2026, read 22 October 2026

What carries over when you build the app?

More than people expect, as long as you count the right things. Your data layer carries over untouched, because the endpoint does not care what asked. Plasmic connects to sources like Supabase, Contentful and Shopify, or to any HTTP or GraphQL endpoint, and a phone app calls those directly. Content in the Plasmic CMS carries over through the documented CMS API, so your writers keep their tool. Your palette, type scale and spacing steps carry over as values. Your component set and variants carry over as a specification, which is the quiet win: the thinking you did in Studio is most of the brief for the app.

What does not carry over is the generated code and the layout. Nobody can convert a CSS grid into a phone screen for you, because the two have different constraints. A 1440 wide marketing page with four columns becomes a stack of cards, and deciding what gets cut is a design job that takes an hour per screen and is worth doing properly. The other item to settle early is payments, which change shape on a reviewed platform in ways a Plasmic checkout never had to.

Newly is an AI app builder for this part. 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 anywhere you cannot reach it. 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. Apple 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, so that step is yours, and the mechanics are in publish to app store.

One honest closing note. If what you have in Plasmic is a marketing site and a contact form, you probably do not need an app at all, and an install is a worse way to read a landing page than a link. Rebuild when you need the icon on the home screen, the camera, a notification, or a screen that works with no signal. Those four jobs are the only reasons worth the review cycle, and if none of them is on your list, keep publishing from Studio. Readers who want the opposite case, a visual tool that already thinks in phone screens, will find it in mit app inventor to mobile app.

Apple, App Store Review Guidelines, guideline 4.2.6, last updated 16 October 2026, read 22 October 2026