I know what you're thinking. "Coding on a phone. Sure. And I'll design a database schema on a napkin while I'm at it."
Fair. It sounds absurd. A phone has a 6-inch screen, a keyboard designed for texting your mom, and no mouse. These are not the tools of a professional software developer.
And yet.
Here's how they do it, and how you can too. This isn't theory. It's a practical guide to the workflows that actually work on a phone.
Rule 1: You're the Architect, Not the Typist
The single most important mental shift for mobile coding is this: stop typing code. I'm serious. Your phone keyboard outputs roughly 40 words per minute. A laptop keyboard does 80-120. You will never win a typing race on a phone. So don't race.
Instead, describe what you want to the AI agent. Be specific. Be opinionated. Give it context. Then review what it produces.
What you dictate (on your phone): "Add a sprint for a new get users endpoint. Follow TDD and write failing tests first. Included pagination with query params for page and limit. Default to page 1 limit 20. Filter by role if role query param is provided."
What the agent does: Reads your schema. Reads your existing route patterns. Creates the endpoint. Adds input validation. Adds the TypeScript types. Runs npm run build to verify it compiles.
What you do: Review the diff. Tap approve. Push to Git. Total phone typing: 0 words. Total code produced: ~80 lines.
That ratio — a few spoken sentances of direction producing 80 lines of code — is the entire reason mobile coding works. Your brain does the hard part. The AI does the mechanical part. The phone is just the communication channel between them. But you still get to review the code and push it to the real git repo.
Rule 2: Learn the Three Panels
PropelCode has three panels you swipe between: file explorer (left), code editor (center), AI chat (right). On a phone, you see one at a time. On a tablet in landscape, you see two. On a desktop browser, you see all three.
The key insight is that you don't need to see them all at once on a phone. A phone is a single-focus device. You're either browsing files, reading code, or talking to the AI. Trying to do two things simultaneously on a 6-inch screen is a mistake. Embrace the sequential workflow: navigate, read, instruct, review.
Rule 3: Git Is Your Superpower
Here's something that surprises people: Git workflows on mobile are actually faster than on desktop. Why? Because PropelCode's Git panel is designed for touch. Stage a file with a tap. Write a commit message (or let the AI write one for you). Push with a button. No terminal commands to remember. No git add -p gymnastics.
You notice: A Slack notification about a CSS regression on the dashboard.
You do: Open PropelCode. Navigate to the CSS file. Tell the AI: "The sidebar width is overflowing on screens below 768px. Fix it by adding a max-width constraint and overflow-x: hidden to the .sidebar class."
Agent does: Reads the file. Makes the fix. Shows you the diff.
You do: Review the two-line change. Approve. Go to Git panel. Stage. Commit with AI-generated message: "fix: constrain sidebar width below 768px to prevent horizontal overflow." Push.
Total time: 3 minutes. From Slack notification to merged fix. On a bus.
Rule 4: Use the Terminal for Verification
The terminal isn't where you do most of your work on mobile. It's where you verify your work. Pull up the terminal drawer, run npm test, confirm everything passes. Run npm run build to make sure TypeScript is happy. Start the dev server to see your changes live.
The Smart Toolbar — that floating bar above the keyboard with { } ( ) = > | / tab — makes terminal commands tolerable on a phone. You won't write a bash script from your phone. But you can absolutely run npm test -- --grep "user endpoint" to verify that the code the AI just wrote actually works.
Rule 5: Know When Not to Use Your Phone
Mobile coding is not for everything. Here's the honest breakdown:
Great on a phone: Bug fixes (especially CSS). Adding a single endpoint or component. Reviewing and approving AI-generated code. Git operations. Quick refactors with AI assistance. Writing commit messages. Reading and understanding code. Code reviews.
Painful on a phone: Large-scale refactoring across 20+ files. Pixel-perfect UI design work. Debugging complex race conditions. Writing extensive documentation. Anything that requires comparing two files side-by-side for extended periods.
The pattern: If you can describe the task in 2-3 sentences and the AI can execute it, your phone is perfect. If the task requires constant back-and-forth visual comparison across multiple files, wait for a laptop.
Three Workflows That Actually Work
After months of using PropelCode daily, these are the three workflows we reach for most:
1. The drive-by fix. You spot an issue — a bug report, a typo, a broken link. Open PropelCode, tell the AI what's wrong, review the fix, push. Under 5 minutes. This is the bread and butter of mobile coding.
2. The architecture session. You have 20 minutes and a clear head. You tell the AI: "I want to add a caching layer for our database queries. Here's my thinking..." and have a technical conversation where the AI writes code and you review it. You might not finish in one session, but you make real progress on a branch you can pick up later.
3. The background build. You describe a substantial feature to the AI, kick off the agent, and put your phone in your pocket. The agent works in the background — creating files, running tests, fixing errors. You get a notification when it's done. You review the complete result later. This is the most powerful workflow because it turns dead time into productive time without requiring your attention.
Mobile coding works. Not for everything, not for everyone, but for the developer who has more ideas than desk time, it changes the game. The gap between "I know how to fix this" and "I fixed it" shrinks from hours to minutes.
Try it. Open PropelCode. Clone a repo. Tell the AI to fix something small. Push the fix. The first time you ship code from your phone and see the commit on GitHub, you'll understand.