For a long time, opening NAOMS on a phone felt like using a desktop that had been shrunk to fit. The shapes were right, but the gestures were not. You were holding a phone and being handed a smaller version of something built for a mouse.

That is over. Open NAOMS on your phone today and it feels like a phone. Your apps are a stack of cards you swipe through, with one calm bottom toolbar that stays put underneath them — the way a phone is supposed to work. This is live now, checked on a real device, and it is simply what NAOMS on a phone is.

Your apps, stacked and swipeable

Instead of hunting through menus, your open apps sit as a stack of cards. You swipe between them. The one you want comes to the front; the others wait behind it. Along the bottom is a single toolbar that belongs to the phone, not borrowed from a desktop — one steady place to move around from, always in reach of your thumb.

The small thing that makes it feel finished is this: each app keeps its own place. When you swipe away from an app and come back to it later, you land exactly where you left off — the same view, the same spot, not a fresh start that forgot where you were. Jump to another app, deal with it, swipe back, and the first one is still holding your place. Nothing is thrown away just because you looked somewhere else for a moment.

The Files app, on a real mobile toolbar

The mobile Files app opens the same way. You can browse through your files and view them from a proper mobile toolbar and menus — not a desktop layout squeezed onto a small screen, but controls that were built to be tapped. It fits into the same stack of cards as everything else, and it keeps its place the same way when you swipe away and back.

One codebase, two shapes

Underneath, the phone is not running a separate, second-rate copy of NAOMS. It is the same NAOMS you use on a larger screen — one body of work that knows how to wear two shapes. The desktop layout and the phone layout come from the same place; the phone simply presents itself as a stack of swipeable cards with a native toolbar, and remembers where each app was. That is why the two keep pace with each other instead of drifting apart: there is one thing here, showing up correctly for the device in your hand.

What we are still building

Here is the honest edge, stated plainly. On your phone today you can browse and view your files — but you cannot yet upload one from the phone itself. That last piece is not wired up. If you want to add a file into NAOMS right now, that still happens from a larger screen; the mobile side is read-and-view for the moment. We are building the upload path, and when it is real we will say so — not before.

One more piece of plain honesty about how we know all this. We have proven the phone experience at phone size, driving the real interface as a real person would tap and swipe through it. Testing the exact feel of every gesture on the full range of physical devices is still limited — so we are confident in what we ship here, and we keep checking it on real hardware rather than assuming it holds everywhere at once.

So the promise we can stand behind today: NAOMS in your pocket finally feels like it belongs there. A stack of apps you swipe through, one native toolbar, each app holding the spot you left it in — and a Files app you can browse and view from a real mobile toolbar. Uploading from the phone is on its way, and we will not pretend it is here until it is.

Related: A canvas you can compose in · Week 17.

Written by AI agents from real project logs; owned and edited by Mujo.