Tauri Goes Mobile

"The core comes along for free. The shell is where mobile asks for real work."

The Promise, Precisely

Tauri 2's headline feature is mobile: the same Rust core and the same webview frontend can build for iOS and Android, not just desktop. This is genuinely the same two-process architecture you've learned — a native Rust process and an OS webview — running on a phone. It is not a transpile to SwiftUI or Jetpack Compose, and it is not your desktop .app running unchanged. It's your existing code, retargeted.

What Transfers, What Doesn't

The deep parts come along almost for free: your commands, invoke, serde serialization, state management, and most of your Rust logic compile and run on mobile. What needs real rework is the shell: the UI must suit touch and small screens, there's no desktop multi-window model, the app lifecycle is harsher (the OS suspends and kills aggressively), and platform concerns like safe areas, notches, and on-screen keyboards appear. Plan to share the core and rebuild the frontend's layout and interaction for mobile.

And a Clear Boundary: Cinder Is Desktop-Only

Everywhere else in this quest, Cinder is the worked example. Not here. Cinder is a macOS desktop creative tool that sits beside Photoshop — mobile is irrelevant to what it does, so it deliberately doesn't use Tauri's mobile support. This track teaches Tauri's reach beyond Cinder. Keep the two separate: when you read 'mobile' here, it's Tauri's capability, not a Cinder feature.

Code

What carries over vs what doesn't·text

Crossing from desktop to mobile:

  TRANSFERS (share it)            NEEDS REWORK (rebuild it)
  ─────────────────────          ─────────────────────────
  Rust commands + invoke          UI layout (touch, small screen)
  serde (de)serialization         no multi-window model
  managed state, events           lifecycle (OS suspends/kills)
  most Rust core logic            safe areas, notches, keyboards
  the IPC mental model            mobile-specific permissions

  Strategy: share the core, rebuild the shell.

Exercise

Take an app idea and split its design into 'core' (logic, data, commands — shareable) and 'shell' (UI, layout, interaction — needs a mobile version). Write what you'd reuse verbatim and what you'd rebuild for a phone. You're practicing the architectural split that makes Tauri mobile worthwhile instead of a second codebase.

Hint

Core = anything in Rust + your data shapes + IPC. Shell = the React layout, navigation, and input handling. The more logic lives below the UI, the more mobile reuses. A UI that's tangled with logic is the thing that makes mobile expensive.