Mapples 2.0 is on its way

The next Mapples release brings every package and the mapples CLI to 2.0.0 together, moves new apps to Expo SDK 58 and adds 20 components that we built while making our app templates.

Release candidates are on npm now under the rc tag. We will post here when the stable release is out.

One version for everything

Until now, the runtime packages and the CLI each had their own version numbers. With 2.0 they move together, so you no longer have to work out which versions fit each other. Apps the CLI creates or syncs depend on @mapples/* ^2.0.0.

New apps start on Expo SDK 58

mapples create now follows the current create-expo-app template:

• Expo SDK 58, React Native 0.88 and React 19.3
• Routes in src/app, with the Mapples folder next to them in src/mapples
• Expo's own icons and splash screen
• React Compiler switched on

Apps you have already linked keep their folders. Nothing moves until you move it.

Real code, in both directions

Every screen on the canvas is real Expo code. Open the code panel on a screen and you see the TSX your app will run, built from the open-source @mapples/* components.

The Home screen of the Echo template in the code panel.

The CLI keeps that code and the canvas in sync in both directions. It can also set up your coding agent, whether you use Claude Code, Cursor or Codex, so the agent and the canvas work on the same project.

20 new components

We built ten complete app templates and added the components they needed. Among the new components:

• Data: bar and line charts, activity rings and a calendar heatmap
• Media: a waveform seek bar, playback controls and a mini player
• Input: a day picker, time picker, range slider and numeric keypad
• Content: ticket cards, a masonry grid, a reorderable list and a map view

Echo uses the new mini player, waveform seek bar and playback controls.

Nine more font families ship with this release too. The map view uses react-native-maps, so Android apps need your own Google Maps key.