
Mapples 2.0 is out
Mapples 2.0 is out. Every @mapples/* and @mapplesorg/* package and the mapples CLI went to 2.0.0 together on October 30. We have shipped patch releases since then: the packages are at 2.0.4 and the CLI is at 2.0.2.
Here is what changed in Creator, the packages and the CLI.
A canvas that follows your navigation
Screens are laid out as a storyboard of your navigation tree, with a row per section and nested sections below. Each frame shows the header and tab bar its screen runs under, so the frame matches what Play and the exported app render.
- One device for every frame. The device picker sets every frame at once. iPhone 18 Pro (402×874) is the new default, next to iPhone Air, iPhone 18 Pro Max, Galaxy S26, Pixel 11 and Pixel 11 Pro XL.
- Light and dark preview. Switch every screen between modes from the zoom badge, without touching the theme.
- Code is one key away. The
</>button on a frame header, or ⌘E (Ctrl+E), opens the screen's source. - Code edits merge. Saved code goes out as git-style hunks with a 3-way merge, and History shows the +/- lines of each edit.
The Sum template in Prototype mode: the Auth stack with its Sign in and Sign up screens.
Play runs your app
Play is a new device overlay in Develop and Prototype modes. Navigation runs with the real stack, tabs and drawer, presses run their actions, and vars.* and api.* are live. Restart resets all of it. Each device gets a realistic phone with a status bar that follows the theme, and a camera button saves a 3× PNG of the screen (web only).
The Overview screen of Sum running in Play.
Routes, guards and your own tab bars
- Routes have a
pathwith params, like/product/:id. The params are inroute.*. - A route can run an
onEnteraction, and an access guard sends people to a fallback route. A guard on a section protects every screen in it. - Design the tab bar or the drawer as a saved component, or ask for native tabs in the exported app.
Connect APIs
Import requests from cURL, OpenAPI 3, Swagger 2 or Postman with the new @mapples/api-import package. Bind responses with api.*, run them with the Run API request action, and preview each screen's Loading, Success and Error states before your server is ready. The canvas calls the API only in Develop with Live data on.
Requests from three formats become bindings, actions and data states.
AI on the canvas (Beta)
The assistant builds an app in four steps: pick a style direction, apply it as a design system, review the plan, then build screen by screen. Each turn lists its changes, and you can revert it. Resolve in AI turns a review comment into a turn, with the comment's screen as context.
Two-way code sync and your own agent
The mapples CLI creates an Expo app linked to your project and keeps the generated TSX and the canvas in sync in both directions. It never overwrites a file you wrote. mapples watch syncs live, and --agent claude, cursor or codex sets up your coding agent with Mapples skills and a read-only MCP entry.
A few of the CLI 2.0 commands.
You can also connect Claude or another MCP client to your projects at https://prod-us.mapples.org/mcp/, and import several Figma frames at once, with an option to rebuild them with AI.
Share and comment
Share a link that opens the app with Play. Reviewers can leave pinned comments without an account. Workspaces now have members, roles and email invites.
Expo SDK 58 and 20 new components
Apps created by the CLI start on Expo SDK 58 with React Native 0.88 and React 19.3. @mapples/components adds 20 components, from charts and calendars to a mini player and a map view. Our earlier post, Mapples 2.0 is on its way, has the details.
Upgrading an app
Update your @mapples/* dependencies to ^2.0.0, then run npx mapples doctor and npx mapples sync. Two changes need edits in existing code: codegen imports library components from @mapples/components instead of @mapples/ui, and MapplesNavigation needs a backend prop on SDK 58.
Try it
Start for free or read the docs: Prototype and Play, Connect an API and Build in your agent.

