I built a SaaS almost entirely from my phone while commuting to my 9-5. Not really as a flex. It’s just the only time I had. My 9-5 takes most of the day, so the bus/metro rides basically became my dev time. Sometimes I also wrote things during work breaks… and occasionally while walking to the restroom 😅 At home I usually work on mobile apps anyway, so building things from a phone didn’t feel that strange after a while. The only thing I actually needed a PC for was publishing the Flutter package to pub.dev. Honestly if there was a way to do that from a phone, I probably would have done that too. Everything else — backend, frontend, database, deployment, domain, DNS — was done from my phone. So yeah, technically not 100%, but close enough that I still say I built it from my phone. ⸻ The main tool that made this possible was Claude Code on iOS. I mostly used the Code tab in Claude AI from my phone to work on the web/backend side of the project. Most of the time I was thinking about the system design and giving fairly long tasks. Because many of the tasks were fairly big, I often asked Claude to propose a plan first and break things into steps before writing code. I did actually review those plans carefully before moving forward. Typical flow looked something like this: • think about architecture • sometimes ask Claude to propose a plan • review the plan • implement the feature • test the endpoint • check logs on Railway / Vercel if something looked wrong • push to GitHub Rinse and repeat. The implementation was basically me + AI going back and forth. Honestly the hardest part was debugging logs on a phone screen. Another surprisingly annoying part was API keys and environment configs. Copy-pasting keys and wiring env variables on a phone takes way longer than it should. ⸻ Development time was around 3–4 weeks, but that’s mostly commute time. Actual coding sessions were short — usually 20–30 minutes during the ride. Looking at the repo now, it ended up being 128 commits, and the first commit was 22 days ago. Most commits are pretty small since I was working in short bursts. I also didn’t track tokens very precisely. I’m on the $20 Claude plan, and I’d guess the total usage for this project was maybe around $10 worth. ⸻ One thing I noticed while working like this is that Claude sometimes repeats questions that were already answered earlier in the same chat. Occasionally I’d say something like “it’s already in the history”, but it would still ask again as if it couldn’t see that part of the context. Because of that, what worked better for me was letting Claude generate proper README / docs and continuing from there, instead of relying only on the chat history. That made the workflow much smoother. ⸻ What I actually built It’s something I called Intyx Dynamic Widget. It’s basically a signal-driven widget system for Flutter apps. Instead of writing stuff like: if user.isPremium show X else show Y all over your app, the app sends signals (segment, sessions, campaigns etc.) and the backend decides which widget to return. So you can change UI behaviour without releasing a new app build. Right now it has things like banners, carousels, countdowns, polls, ratings, etc. There’s also a dashboard and a Flutter SDK. ⸻ Stack is pretty simple: backend → Python + Flask database → Firestore AI → Gemini dashboard → React + Vite hosting → Railway + Vercel And all the code lived on GitHub, which I managed from my phone. ⸻ The only thing that forced me to touch a computer was: dart pub publish because you need the Dart SDK locally to publish to pub.dev. Other than that everything worked fine from mobile. ⸻ Funny thing is that after I started building it, I discovered that some similar ideas already exist. Tools like GenUI or TheSys are doing somewhat related things. I actually didn’t know about them when I started. If I had researched more I probably would’ve found them earlier, but at that point I was already curious and halfway in, so I just finished the project anyway. ⸻ This started mostly as an experiment out of curiosity, but it worked better than I expected. For the mobile development side, I’m planning to try doing that directly from the phone as well using an agent in the future. Haven’t done that part yet, but that’s probably the next experiment. ⸻ Anyway, the project is still very early and experimental, but it works. I’m not saying building SaaS from a phone is ideal. But if that’s the only time you have… turns out it’s actually possible. For my next SaaS or web apps I’ll probably research more first, but I’ll likely still build them the same way — phone + AI during commute. ⸻ If anyone’s curious I can also explain the exact mobile workflow (tools, debugging, git, etc). Links if anyone wants to check it out: Website dynamic.intyx.ai Flutter package pub.dev/packages/intyx_dynamic_widget submitted by /u/piseqqq
Originally posted by u/piseqqq on r/ClaudeCode