I Spent a Week Coding on My Phone With Codex Appshot — I Have Regrets (and One Surprising Win)

So apparently "mobile remote programming" is a thing now. An actual thing people are doing. On purpose.

My thumbs have filed a formal complaint with HR.

I stumbled across a Reddit thread last week where someone was absolutely losing their mind over this Codex Appshot app for mobile remote coding. My BS detector went off immediately — I've been burned by "revolutionary" dev tools before. But I was trapped on a 6-hour Amtrak ride from hell (wifi somehow worse than dial-up, genuinely impressive in 2024), armed with nothing but my phone and a burning hatred for the legacy PHP monolith I was supposed to be debugging. Figured I'd give it a go.

Spoiler: it's not the dumpster fire I expected. But it's also not replacing my ultrawide setup. Ever. Probably.

What It Actually Is (The "Explain It Like I'm 5" Version)

For those who haven't fallen down this particular rabbit hole — Codex Appshot is basically a remote dev environment running on your phone. Think VS Code Server meets TeamViewer, except someone actually spent more than 30 seconds thinking about touchscreens.

You're not compiling anything locally. Thank god. My Pixel 7 would probably melt through the train floor and take out a carriage. Instead, you're remoting into a container somewhere that does all the heavy lifting.

The pitch: fix production bugs from literally anywhere.

The reality: you'll mostly use it to change a config value while sitting on the loo at 11pm because your on-call rotation hates you personally.

One thing worth clarifying — when I say "container," I mean a dedicated environment per session. Not shared. I'm paranoid about this stuff. Checked their docs obsessively on day 3. It's properly isolated.

The Good Parts (I'm as Surprised as You Are)

1. The Autocomplete Is Weirdly Good

I was expecting garbage mobile keyboard predictions — the kind where you type "def" and it suggests "definitely."

Nope.

They've done something clever with context-aware suggestions that actually understands I'm writing Python and not trying to text my mum about pandas (the animals, not the library). I bashed out a 47-line data processing script with fewer typos than I make on my mechanical keyboard. Still processing that. Not sure what it says about me.

2. Git Integration Doesn't Suck

Managed to squash 3 commits, resolve a merge conflict, and push to a feature branch without wanting to lob my phone into traffic.

The diff viewer has this side-by-side swipe thing that's honestly better than some desktop git clients I've used. Looking at you, GitKraken free tier. You know what you did.

3. Terminal Access Is Real

SSH'd into a prod server (read-only, I'm not a complete masochist), checked logs, restarted a docker container. All from my phone. Felt like a hacker in a terrible film.

Immediately texted my CTO a screenshot. He replied "please don't do that again" at 2:37am. The timestamp haunts me.

The "Oh God Why" Parts

Remember that thread from u/throwaway_devops about mobile IDEs being the future? That bloke was wrong about a few things.

A lot of things, actually.

The biggest issue is screen real estate. You're basically coding through a keyhole. I tried working on a React component with the file tree open and the terminal at the bottom. I could see approximately 4 lines of code at a time.

Four.

It's like coding on a postage stamp. A very expensive, backlit postage stamp that keeps autocorrecting useState to used state.

The connection dropped twice during tunnel sections of my journey. Each time I lost about 30 seconds of work. Not catastrophic, but enough to make me paranoid about saving every 10 seconds like it's 1998 and I'm using WordPerfect.

Remember WordPerfect? I'm old.

And the keyboard situation. Look. I've developed opinions about mobile keyboard layouts that I never wanted to have. The special characters. Where did they put the curly braces? Why are they hidden behind three menus? I spent 45 seconds hunting for a backtick once.

Not my finest moment.

The "I Can't Believe This Actually Worked" Moment

Plot twist.

Around day 4, I got paged at 2am for a database connection pool exhaustion issue. The classic — PostgreSQL, max_connections hit, everything on fire. Normally this means stumbling to my desk, waiting for my monitors to wake up, and questioning every life choice that led me to backend engineering.

Instead, I rolled over, grabbed my phone, SSH'd in through Codex, ran:

SELECT count(*) FROM pg_stat_activity;

Spotted the stuck transactions from that one microservice Dave wrote (it's always Dave's service), and killed them.

Total time: 4 minutes. Went back to sleep. My wife didn't even wake up. The cat did, but the cat's always awake.

That's the actual use case. Not "mobile development" as a primary workflow. It's "oh crap" emergency access when you're away from your machine and the alternative is explaining to your CTO why you couldn't fix the thing.

Real Talk About the Mobile Coding Hype

I've seen a bunch of tech blogs — Chinese and otherwise — pushing this as the next big thing in remote work. Let me be the wet blanket here.

This is a supplement, not a replacement.

You're not going to architect a microservice on your phone. You're not going to do meaningful refactoring. What you WILL do is small fixes, code reviews, and emergency interventions when the universe decides to set your infrastructure on fire at 3am.

Think of it like a spare tyre. You're glad it's there when you need it, but you're not entering the Indy 500 with it. And you're definitely not winning.

I reckon the hype cycle on this is peaking right now. Give it six months and we'll all forget this was supposed to be revolutionary.

The Pricing Elephant in the Room

It's subscription-based. Shocking, I know.

Free tier gives you 10 hours/month of container time — honestly enough for the emergency use case I described. Paid tiers go up from there. I think it's roughly $12/month (about £9.50) for the next tier? Something like that. I'm still on free tier and haven't hit the limit yet.

Your mileage may vary if you're actually trying to use this as a daily driver. Which you shouldn't.

Quick Comparison to Alternatives

Tried GitHub Codespaces on mobile browser before this. Technically possible, but the UX fights you at every step. Pinch to zoom. Accidental clicks. Pure suffering.

Also tried just SSH'ing through Termius and using vim. That was a dark afternoon I don't want to talk about. Let's just say I learned things about vim that no one should know. :q! is burned into my muscle memory in ways that feel unhealthy.

Codex Appshot at least pretends to care about mobile users. The bar is on the floor, but they cleared it.

Key Takeaways (TL;DR)

• Surprisingly functional for emergency fixes and small changes
• Terrible for actual development work — physics is undefeated
• Free tier is worth having in your back pocket if you're on call
• Don't try to write a full-stack app on your phone unless you hate yourself. And your thumbs.
• It's a spare tyre, not a Formula 1 car

Edit: Since people are asking — yes, it works on both iOS and Android. I tested on a Pixel 7 running Android 15 beta. No, I don't work for them. Yes, I still prefer my desktop setup with 3 monitors and an ergonomic keyboard that cost more than my first car (a 2003 Corolla, if you're curious).

Edit 2: Thanks for the gold, kind stranger. My most upvoted comment is now about coding on the loo. This is my legacy. My mum is so proud.

Edit 3: A few people asked about security. I'm not a security engineer, but from what I've seen, the SSH keys are stored client-side and the containers get wiped between sessions. Someone smarter than me should probably audit this properly. Don't @ me.

What's your "I fixed production from the weirdest place" story? Bonus points if it involves a phone, a beach, and questionable life choices. Mine involves a wedding reception and a very angry mother of the bride. But that's a story for another post.

Drop your war stories in the comments. I need to know I'm not alone in this madness.

programming #remotework #mobileDev #DevOps #onCall #warStories