能应急改bug，但别指望替代电脑

---

Experience: I tried coding on my phone with Codex Appshot for a week so you don't have to

TIL that "mobile remote programming" is apparently a thing now, and my thumbs have never felt more personally attacked by my career choices. Saw a thread last week where someone was absolutely losing their mind over this Codex Appshot thing for 手机远程编程 (mobile remote coding), and my BS detector immediately went off. But I was stuck on a 6-hour Amtrak ride from hell—the wifi was somehow worse than dial-up—with nothing but my phone and a burning hatred for the legacy PHP monolith I was supposed to be debugging, so I figured why not.

Spoiler: it's not the dumpster fire I expected, but it's also not replacing my ultrawide anytime soon. Or ever, probably.

What it actually is (ELI5 version)

For those who haven't fallen down this particular rabbit hole yet—Codex Appshot is basically a remote dev environment that runs on your phone. Think VS Code Server meets TeamViewer, but someone actually thought about touchscreens for more than 30 seconds. You're not compiling stuff locally on your phone (thank god, my Pixel 7 would probably melt through the floor), you're remoting into a container somewhere that does the heavy lifting.

The pitch is that you can fix production bugs from literally anywhere. The reality is you'll mostly use it to change a config value while sitting on the toilet at 11pm because your on-call rotation hates you personally.

Actually, wait—I should clarify something. When I say "container," I mean they spin up a dedicated environment per session. It's not shared. I was paranoid about that. Checked their docs on day 3. It's legit 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." But they've done something with context-aware suggestions that actually understands I'm writing Python and not trying to text my mom about pandas. Got through a 47-line data processing script with fewer typos than I make on my mechanical keyboard. Make of that what you will. I'm still not sure what to make of it.

2. Git integration doesn't suck - Managed to squash 3 commits, resolve a merge conflict, and push to a feature branch without wanting to throw 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 bad movie. You know the one. 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? Yeah, that guy 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, and 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.

Also, the connection dropped twice during my train ride through tunnels. Each time I lost about 30 seconds of work. Not catastrophic, but enough to make me paranoid about hitting save every 10 seconds like it's 1998 and I'm using WordPerfect. Remember WordPerfect? I'm old.

The keyboard situation is... well. Let's just say 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 looking for a backtick once. Not my finest moment.

The "I can't believe this actually worked" moment

Around day 4, I got paged at 2am for a database connection pool exhaustion issue. You know the one—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 手机远程编程 hype

I've seen a bunch of Chinese tech blogs 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.

Think of it like a spare tire. 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 think the hype cycle on this is probably 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, which is honestly enough for the emergency use case I described. Paid tiers go up from there—I think it's like $12/month for the next tier? Something like that. I'm still on free tier and haven't hit the limit yet, YMMV if you're actually trying to use this as a daily driver.

Which you shouldn't.

Comparison to alternatives

Tried GitHub Codespaces on mobile browser before this—it's technically possible but the UX is fighting you 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.

Bottom line

Would I recommend it? For the specific use case of "I need to fix something right now and I'm not at my computer"—yeah, actually. It's saved my bacon twice this week. For "I want to code on my phone because it's the future"—go touch grass, seriously.

The tech is solid. The execution is better than I expected. But the fundamental limitation is physics. You can't fit a proper IDE on a 6-inch screen without making compromises that hurt productivity. I don't care how good your autocomplete is.

TL;DR: Codex Appshot is surprisingly functional mobile remote coding that's great for emergencies and small fixes, terrible for actual development work. Free tier is worth having in your back pocket if you're on call. Just don't try to write a full-stack app on your phone unless you hate yourself. And your thumbs.

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 wondering).

Edit 2: Thanks for the gold, kind stranger. My most upvoted comment is now about coding on the toilet. This is my legacy. My mom 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. 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.

#programming #remotework #mobileDev #DevOps #onCall #warStories