Solo Development with
Just a Smartphone
A real-world story of a freelance side-hustle engineer who used Claush to build an AI news service during cafe breaks and while waiting at traffic lights on a jog.
User Overview
A freelance engineer working on solo projects as a side hustle. With limited time to sit in front of a PC, they were searching for a way to complete development entirely from a smartphone.
The Project: News Butler AI
A next-generation RSS reader for smartphones and the web. It analyzes news through user-defined custom analysis criteria and delivers periodic reports as notifications.
| Factor | Why it paired well with Claush |
|---|---|
| Solo development | All decisions are made by one person, enabling instant decisions and implementation via chat |
| Firebase stack | Easy CI/CD setup, allowing the prerequisite environment for the Claush workflow to be established quickly |
| Small project scope | A compact concept with fast launch, perfectly fitting the "break it down small and iterate" style |
Workflow Overview
Aside from the initial environment setup, everything can be done entirely from a smartphone
Prerequisites
The only PC-required work is the initial setup: creating the GitHub repository and configuring the CI environment. From then on, all development is completed using just a smartphone and Claush.
Development Cycle
Benefits
Work from anywhere
Access your development environment from anywhere via VPS.
Intuitive chat interface
Control Claude Code with natural language. No need to memorize commands.
Easy to stay focused
Opening your phone naturally puts you in "development mode."
Fast development cycles
Working in small units keeps reviews lightweight and maintains a good tempo.
Low stress
Even when many revisions are needed, the conversational feel with Claush keeps frustration at bay.
Tips for Making Mobile Development Work
Break tasks into small pieces
Smaller review scope means you can thoroughly review even on a phone screen. As a side benefit, development cycles become faster, leading to a smooth and satisfying development experience.
Think of it as a conversation with Claush
Rather than feeling like you're making something write code, approach it as "building something through conversation." Even on branches with many revisions, you can keep moving forward steadily without stress. Development rarely feels frustrating.
User Testimonials
When I open my phone, I naturally shift into development mode
Through Claush, it feels like having a conversation, and development becomes effortless
I rarely feel frustrated while developing anymore
The Journey to Claush
The ideal development vision they always had
Ever since AI development tools like GitHub Copilot emerged, they had held the ideal of a development style where "you give instructions via chat and review via PRs."
Frustrations with existing services
| Issue | Details |
|---|---|
| Low-quality PRs | Many services send massive, messy Pull Requests that are impossible to review properly |
| Poor chat UX | Even services with chat functionality had poor usability and impractical experiences |
| Gap from the ideal | No service delivered the experience of "building through conversation" |
Claush still has imperfections, but in terms of enabling chat-based conversational development, it comes closest to the perfect vision
Detailed Use Cases
1. At Home - Regular Development
Applies the full workflow cycle described above. Everything from writing specifications to Issue registration, implementation, PR creation, and merging is operated from the Claush chat interface.
2. Development in Spare Moments While Out
A few minutes after ordering at a cafe, a quick bathroom break during a date - you can give instructions in these tiny windows of time
Unlike VS Code, there's no assumption of looking at code directly. By limiting each instruction to one user story, review time stays around 5 minutes, making it possible to complete a merge within a spare moment.
| Scene | Time estimate |
|---|---|
| Right after sitting down at a cafe | 3-5 min |
| Bathroom break during a date | 2-3 min |
| Waiting for a train transfer | A few min |
3. Development While Jogging
Think through ideas while running, give instructions while waiting at a traffic light
A use case that's only possible because Claush goes wherever your phone goes. Physical exercise and development become one seamless activity.
| Timing | Action |
|---|---|
| While running | Organize feature ideas and marketing strategies in your head |
| Waiting at a traffic light | Pull out your phone and type instructions into Claush |
| Catching your breath | Check the chat response and think about the next instruction |
Feature Requests & Missing Functionality
1. Push Notifications
After sending an instruction to Claush, there's no notification when Claude responds. While waiting for a response, it's inefficient because you can't switch to other tasks.
2. GitHub Webhook Integration & Automatic CI Failure Detection
Currently, Claush cannot automatically detect CI failures, requiring manual checking via the GitHub app and then relaying the information back to Claush - an unnecessary extra step and context switch.
Future idea: Strengthening the CI/CD environment
The bottleneck in the "break it down small and iterate fast" workflow is slow CI/CD. Since GitHub Actions' default runners are slow, the plan is to set up self-hosted runners for faster execution.
Feedback Summary
- Being able to operate the entire standard GitHub workflow (Issue β PR β CI β Merge) from chat is what makes mobile development realistic
- The "building through conversation" experience, rather than a "using a tool" feeling, fundamentally reduces development stress
- The "break it down and iterate" development style pairs well with Claush, naturally forming mobile-first development habits
- For freelancers and side-hustle users, there is significant value in terms of maintaining motivation and making it easy to keep going