Vibe-coding used to mean laptop, coffee, and "let me quickly test this idea." Then I realized: my phone is always with me, and ideas don't come on schedule. That's how I developed what I call VibePhone Coding — the entire cycle from idea to deploy happens on my iPhone, literally while walking to work.
This isn't "proper engineering." It's rapid hypothesis testing. In 1-2 hours you can ship a feature or build a small project from scratch.
Why I Do This
Ideas come while moving: on the way, in the elevator, in line. If you don't capture and implement quickly — the idea dies. I don't want to "open my laptop" for 15 minutes of impulse. My goal is a prototype: see how it works in the browser, not perfect code.
Stack and Principle
Main stack: JavaScript / TypeScript, usually Next.js. Repositories on GitHub, Claude Code as the implementation agent, deploy via AWS Amplify (but the logic works for other CI/CD too).
Key point: Main is not production for me. Main = staging, so I can merge fearlessly and see results.
The Workflow
Walking to the office, I dictate the idea to ChatGPT by voice: what I want to do, expected result, constraints, and what files already exist. Then I ask to convert it into a structured prompt for Claude Code — with a step-by-step plan, file list, commands, and definition of done.
From my phone I open GitHub (create new repo or open existing project), launch Claude Code, select the repository, paste the prompt — and keep walking. In 15 minutes the agent has already created the structure, added pages, hooked up forms — sometimes built an entire MVP.
Then — merge to Main. Yes, without classic code review, because the goal isn't quality, it's speed of idea validation. Amplify picks up changes, I open the staging domain on my phone and check the result.
If Something Breaks
I see an error — dictate the problem to ChatGPT, get a prompt to "fix this", create a new branch, merge, check. Iterate like that. Fast. Simple. Bold.
Why This Works
Minimum friction — idea becomes implementation without "get laptop, set up environment." High experiment density — can test more hypotheses in a week than before in a month. Psychologically easier — not "big development," but a series of small jumps. And most importantly: phone is always nearby, so you actually start doing.
Limitations
This approach is not for production development, not for teamwork, doesn't guarantee quality. Dangerous if Main = prod. So the iron rule: Main = staging, production lives separately. Secrets only through env, not in repo. If the project "takes off" — then properly rewrite later.
Final
In fact, I turned my commute into a "pocket lab." I don't write code on my phone in the classic sense — I manage development with my voice, and the agent does the mechanics. VibePhone Coding is not about perfection. It's about speed, excitement, and testing ideas while they're hot.