Pocket-Sized Dev Shop: The Week We Shipped a Web App Using Nothing But an Android Phone
Photo: Lbronn, CC BY-SA 4.0, via Wikimedia Commons
There's a stat that keeps floating around and it deserves more attention from the hosting world: millions of Americans are what researchers call 'smartphone-only' internet users. No laptop gathering dust in the closet. No gaming rig. Just a phone, maybe a tablet, and a data plan. And plenty of them want to learn to code.
So we ran the experiment. One Android phone (a mid-range Pixel, nothing fancy), one week, zero dollars, and a goal: build, deploy, and maintain a working web app without ever touching a laptop. Here's how it went, including which free hosting dashboards treated our tiny screen like a real client and which ones clearly assumed we'd be sitting at a desk with two monitors.
The Toolchain: What Actually Works on a Phone
First, the good news. The phone-only dev stack is more real than most people think:
- GitHub's mobile app handles code review and even basic edits surprisingly well, but for actual commits you'll want the mobile web version of github.dev — a browser-based VS Code that runs in Chrome on Android. It's clunky, but it works.
- Cloud IDEs like GitHub Codespaces (60 free hours a month on a personal account) or Gitpod give you a full Linux environment in a browser tab. Typing code on a touchscreen is miserable until you install Hacker's Keyboard, which brings back Ctrl, Tab, and arrow keys.
- A cheap Bluetooth keyboard is technically against the spirit of the challenge, so we didn't use one. We suffered. You can learn from our suffering instead.
The app itself? A simple waitlist tracker for a fictional neighborhood food truck — a form, a database row per signup, and a public counter. Boring on purpose. The point was the workflow, not the product.
Deploying From a Bus Stop
The actual deployment step turned out to be the easiest part of the whole week. Git push from the phone, and platforms that auto-deploy from GitHub did the rest. Render, Fly.io, Vercel, and Railway all picked up our commits without us ever opening a dashboard on some days.
That's the real lesson for hosting providers: the best mobile experience is the one you barely need. Push-to-deploy is accessibility. If your platform requires clicking through a web dashboard to ship code, you've failed the phone-only user whether you realize it or not.
Grading the Free Dashboards on a 6-Inch Screen
But you can't avoid dashboards entirely. Databases need checking. Logs need reading. Env vars need setting. And this is where the free tiers diverged sharply:
- Railway was the standout. Clean responsive layout, logs that scroll legibly on mobile, and settings that don't hide behind hover menus (which are a nightmare on touchscreens).
- Render's dashboard worked fine for the basics, though log streaming on a phone felt like reading a receipt through a keyhole.
- Vercel is polished, no complaints, though some deeper settings bounce you into flows that clearly assume a wider viewport.
- Fly.io leans hard on its CLI, which is powerful — if you can get a terminal running on your phone. Codespaces made it possible, but it added an extra hop to everything.
If you're a phone-only developer, favor platforms where the CLI can be replaced by a decent mobile web UI for the common tasks. You'll thank yourself at 11 PM when something breaks and all you have is your phone and a questionable Wi-Fi connection at a Denny's.
What's Miserable (Be Honest With Yourself)
Let's not sugarcoat it. The pain points are real:
- Typing. Even with a good keyboard app, writing code on glass is roughly half the speed of a real keyboard and three times the typos.
- Debugging. Comparing a stack trace to your code means constant app-switching. Split screen on Android helps, but you're working in a postage stamp.
- Battery. Codespaces plus Chrome plus hotspot ate about 20% an hour. Carry a power bank or don't bother.
- Mystery errors. Some OAuth flows and dashboard modals simply break on mobile browsers. When that happened, we were stuck until we could borrow a laptop — a reminder that 'phone-only' still has cliffs.
The Verdict
The app shipped on day three and stayed up the rest of the week, serving a handful of test signups without a hiccup. Total spend: $0. Total laptops used: zero.
Is this how anyone should build a serious project? No. But can a motivated person with only an Android phone learn to code, deploy to a free tier, and run something real? Absolutely — and free hosting is the reason it's possible. If you're in the smartphone-only camp, pick hosts with push-to-deploy and responsive dashboards, grab a Bluetooth keyboard when you can afford it, and know that the ceiling is higher than the industry assumes.
Now if you'll excuse us, our thumbs need a vacation.