We're building native iOS and Android apps

We decided on 22 October 2026 to build two native phone apps, one for iPhone and one for Android, both from scratch. They won't be the web app squeezed to phone width, or one codebase wearing two costumes. We're planning them for November 2026.

Until then, the web app is how you use Shuriken on a phone.

Why native, and why now#

Most of the time, the phone is where you check on your agents: what finished, what's waiting for an approval, whether to send one more instruction before your coffee is ready. The visits are short, and in a short visit every bit of friction shows.

The web app does the job, but a browser only gets so close. The keyboard and the composer never quite agree. A back swipe isn't the system's back swipe. The menus don't look like the rest of your phone. Each of those is small, and together they make it feel like a website, because it is one.

You can't fix that with more CSS. So we're writing the apps the way each platform expects.

iPhone, in iPhone style#

The iPhone app will follow Apple's design guidelines and the Liquid Glass look of iOS 26: the system tab bar, sheets that slide up to the right height, real menus on a long press and haptics that match what you did. If it looks like an app Apple could have shipped, we got it right.

Android, in Android style#

On Android we're using Material 3 Expressive, Google's current design language, with predictive back, bottom sheets and a top bar that folds away as you scroll. It will use the system's haptics too. We don't want it to be the iPhone app with the corners changed.

What matters on a phone#

We're not squeezing the desktop app into a pocket. The phone apps are planned around three things people actually do there:

• read a long answer and reply quickly;
• queue the next message while the agent is still busy;
• tap Allow or Deny when it asks.

Then there's the feel. The composer sits on top of the keyboard, never under it, and a back swipe goes back. Rows get swipe actions where they make sense. Pickers and approvals come up from the bottom, where your thumb already is. Sending gives a light tap, and approving or a failure gives a different one.

One thing stays the same: the phone doesn't run your agents. Claude Code, Codex and the rest keep running on your computers and servers, and the phone follows them and steers them. That's how Shuriken works everywhere, and the phone guide explains the setup.

Timing#

We held phone work until Shuriken 5.1.0 was out, so 5.1 got our full attention. We're aiming for both apps in November 2026.

On this site you'll see App Store and Google Play badges, greyed out and marked as coming. When they light up, they're real. The iOS and Android pages will have the details as they firm up.

Until then: the web app#

Open app.shuriken.sh in any phone browser and add it to your home screen. You get every chat, the queue, Changes and voice. Browsers never count toward your linked devices, and it works on every plan, Free included. Our post on the phone web app has the details, and the phone feature page shows what's in it.

The phone needs a computer to talk to, so if you haven't yet, try Shuriken on your Mac, Windows or Linux machine first.