A week of work with a phone and no laptop

The phone in your pocket has more processing power than the laptop you used five years ago, a better camera than any of them, and every file you own. And yet a week of actual work on it is genuinely harder than a week on a laptop, for reasons that have almost nothing to do with performance.

Using a phone as computer is possible for a wider range of work than people assume, and it fails in specific, predictable places. Knowing which is which turns it from an experiment into a decision you can make deliberately — for a trip, for a day out of the office, or permanently for some kinds of work.

What works better than expected

Using a phone as computer is genuinely competitive in five categories, and wins outright in two.

• Communication. Email, messaging, calls, scheduling. Phones were built for this, and the mobile versions are frequently better than the desktop ones.
• Reading and reviewing. Documents, articles, pull requests, contracts. Reading is reading, and the phone is more comfortable to hold.
• Capture. Photos, scans, voice notes, quick text. This is the category where a phone wins outright, because the device is already in your hand and a laptop is not.
• Approvals and short decisions. Anything that is a yes or no with context attached.
• Media consumption and light editing. Cropping, trimming, adding text.

The phone wins whenever the task starts with something in the physical world — a document to scan, a moment to record, a signature to give. The laptop wins whenever the task starts with a blank screen.

That distinction predicts most of the rest of this article.

Where it stops

A phone as computer hits four walls, and only one of them is about the screen.

Long-form writing. Not impossible — an external keyboard changes it substantially — but the editing loop of moving between paragraphs, referring to another document and reorganising structure is where touch is genuinely slower.

Anything with many windows. Comparing two documents, referring to a spec while writing code, watching a log while clicking a button. Split view helps and does not close the gap.

Precise pointing. Detailed image work, spreadsheets beyond a few columns, timeline editing. A finger is roughly a centimetre wide and a cursor is a pixel.

File-heavy work. Bulk renaming, organising hundreds of files, working with archives. The mobile file managers are capable and slow at volume.

What actually makes it viable

Five changes make a phone as computer viable, in order of how much difference each makes.

1. An external keyboard. This single item moves more tasks into the possible column than everything else combined, and a folding one weighs almost nothing.
2. A way to prop the phone up. Holding a phone while typing on a keyboard is unworkable; anything that stands it at an angle fixes it.
3. Cloud-based or synced files. If your work lives only on a laptop's disk, the phone cannot reach it, and that is the end of the experiment before it starts.
4. A password manager with autofill. Typing complex passwords on a phone is where people abandon this.
5. Text expansion or shortcuts. Canned replies, signatures, common phrases. Typing is the bottleneck, so anything that types for you compounds.

Points one and two together cost very little and are the difference between "I answered email" and "I did a day's work".

Building the workflow around capture

The strongest argument for a phone as computer is that it is present when the work appears.

Scan rather than photograph. A document scanner produces a straightened, compressed PDF that is smaller and more legible than a camera photo of the same page, and it names and dates it.

Record instead of writing when the input is verbal. A voice note taken immediately is more accurate than a summary written an hour later, and transcription turns it into text you can search.

Turn photos into documents. Text recognition in the photo library means a picture of a whiteboard becomes searchable text, which is a genuinely new capability rather than a mobile version of an old one.

Send to yourself deliberately. A single inbox — a note, an email to yourself, a folder — beats items scattered across apps you will not remember to check.

The last point is what separates a productive phone workflow from a pile of screenshots. Capture is easy; the discipline is in having one place things land.

What about a tablet instead?

The obvious middle option, and it changes the calculation in specific ways rather than generally.

A tablet fixes the screen size and, with a keyboard case, the typing. It does not fix the two constraints that actually matter most: window management is better but still limited, and precise pointing improves only if a trackpad or stylus is attached. What it does add is a real cost — it is a third device to carry, charge and keep in sync, and it is often carried alongside the phone rather than instead of it.

The honest comparison, for a week away from a desk:

• Phone alone. Lightest, always present, hardest for sustained work. Best when the trip is mostly meetings and movement.
• Phone plus folding keyboard. Nearly as light, and it covers email, documents and short writing comfortably.
• Tablet plus keyboard. Approaching a laptop for most tasks and heavier than the previous option by a real margin.
• Laptop. Everything works, and you carry a laptop.

The option people underrate is the second. A folding keyboard weighs less than a paperback and it converts the phone you were carrying anyway, which means nothing extra is charged, synced or left in a hotel room.

The option people overrate is the third, when the tablet ends up doing the same tasks the phone would have done, with more to carry.

The week in practice

If you are trying this deliberately, four things worth planning.

Do the writing-heavy work first, on a laptop, before you leave. Trying to do it on the phone is where the week fails.

Check the specific tools you need on a phone, not the category. "Email works" is true; "the expense system works in a mobile browser" often is not, and finding out on the day is expensive.

Expect the file transfer step to be the friction. Getting a finished file from the phone to wherever it needs to go is more steps than on a laptop, and it is worth setting up before you need it.

Watch the battery. A phone doing a day of work is a phone at 20% by mid-afternoon, and a power bank is not optional.

Two things are worth trying even if you never do the full week: a day of meetings with only the phone, and a week where all capture happens on it regardless of where the work is finished. The second changes habits permanently for most people who try it.

More workflow pieces in digital workflows, the tools themselves in productivity, and general picks in online tools. Apple's multitasking guide covers the split-screen features that close part of the gap.

The short version

A phone as computer works for communication, reading, review, approvals and — better than a laptop — anything that starts in the physical world. It stops at long-form writing, multiple windows, precise pointing and bulk file work.

An external keyboard and something to prop the phone against move more into reach than any app does. Do the writing before you leave, verify the specific tools you need rather than assuming the category works, and build the workflow around capture — because being present when the work appears is the one advantage a laptop cannot match.