Galaxy Watch Ultra for work: LTE, standalone apps and useful settings

The Galaxy Watch Ultra is sold as a sports watch. Set up deliberately, it is one of the better work devices you can wear, mostly because it can leave the phone behind. This is the setup that makes it useful on a working day, in the order you should do it.

Is the Galaxy Watch Ultra good for work?

Yes, for a specific kind of work: the kind where you need to be reachable for a few important things and otherwise left alone. A watch cannot replace a laptop and should not try. It can deliver the pager, show a two-factor code, take a short dictation and answer a yes/no question, all without you taking a phone out, and the Ultra does those things with a bigger battery and better input than the standard Galaxy Watch.

What it is not good for is anything that takes typing or reading at length. Replying to an email from a watch is possible and nobody does it twice. Treat the watch as the place where decisions arrive and the phone as the place where reading happens, and the setup below follows naturally.

The rest of this guide is the setup in order: connectivity first, then notifications, then input, then battery, then the apps.

LTE: does it work without the phone?

The Ultra's LTE variant has its own connection, so calls, messages and standalone apps work with the phone in a drawer. For work, that means the pager reaches you on a run, the two-factor code is on your wrist in the server room, and an agent supervision app talks to your relay from anywhere.

1. Enable the eSIM with your carrier's number-share plan, so the watch answers to the same number as the phone.
2. Turn on Wi-Fi calling for buildings with bad signal.
3. Check that the apps you need are standalone rather than phone companions; a companion app stops working the moment the phone is out of Bluetooth range.

On Wi-Fi the Bluetooth model behaves identically. LTE is for the gap between networks: the walk, the commute, the car park.

Two things to check with your carrier before you rely on it. Number-share is usually a monthly add-on to the phone's plan, and not every plan or every carrier offers it. And LTE on a watch costs battery, which is why the battery section below says to leave it on demand rather than always on.

PeakWatch does this from your own data. Your coding agent, on your wrist. Join the free beta →

Notification triage

Default notification mirroring makes the watch unbearable. Allow only the apps whose alerts you would answer in a meeting. Everything else stays on the phone.

Use Modes for focus blocks so that only the pager gets through. The watch is at its best when a buzz always means something, and the apps worth installing are the ones that respect that.

The last two rows are the ones that matter for anyone running coding agents. A session that is working should be silent. A session that has stopped and needs a decision is the one buzz you want, and it should carry enough context to answer from the wrist: the tool, the file or command, and the reason.

The bezel and the buttons

The bezel ring is the Ultra's best input: run a finger around it to scroll lists, dismiss notifications and move through screens without covering the display. Apps built for recent Wear OS use it properly; PeakWatch, for example, scrolls sessions and conversations with it and detents on each row. The side buttons handle back and home; learn them once and you will rarely touch the screen in a corridor.

Three gestures cover most of a working day. A swipe from the face reaches your tiles: the authenticator, the calendar, the session list. A finger round the bezel scrolls whatever is on screen without covering it. A long press on the side button opens the assistant for dictation, which is how a reminder or a prompt leaves the wrist. Everything else is a tap.

Battery habits

Two to three days between charges is realistic with standalone apps in use, if you change four defaults.

If you do train with it, the heart-rate setting is the one to flip back; your zones need continuous sampling during the session and nothing else does.

Charge it while you shower or while you are at the desk, not overnight; that is when a work watch is least useful and the one time it is guaranteed to be near a charger. Half an hour on a desk charger each morning keeps it topped up without a nightly ritual, and a watch that is charging at 3 a.m. is a watch that misses the pager.

Standalone apps worth installing

An authenticator with a tile; a notes app with voice input; a calendar complication; and, for anyone who runs coding agents, PeakWatch, which lists your Claude Code sessions, takes approvals and prompts, and shows plan usage, all over LTE with no phone in the loop. It is in private beta, so for now that is a waitlist.

Install fewer than you think. Every standalone app you add is another connection on LTE and another thing that can buzz. The test is the same as for notifications: if you would reach for it in a corridor, it earns a place; if you would open the phone anyway, it does not. Four or five apps is a working watch; fifteen is a slow one.

Setting it up for coding agents

If the reason you want a work watch is that an agent keeps needing you, there are two layers. Anthropic's Remote Control puts a Claude Code session in the Claude app on your phone, with permission prompts forwarded and push notifications when it needs a decision; the setup is a one-line command. PeakWatch puts the same session on the wrist with a sixty-second auto-deny and no phone required.

Either way, the point is supervising without sitting at the desk, and the Ultra's LTE is what makes that possible on the move.

The order matters. Set up Remote Control first, because it needs nothing but a command and a scan, and it gives you the full conversation and the diff on the phone when you want them. Add the watch for the moments when the phone is not in your hand: the kitchen, the gym, the meeting where a glance is acceptable and a phone is not.

Hen Eytan · Founder, UPeak

Builds the UPeak apps and writes up the research behind them.