WF-001: Mobile Development Workflow

DOCUMENT CONTROL

Field	Value
WF ID	WF-001
Version	1.0
Status	Active
Last Updated	December 2025

Overview

This workflow describes the complete cycle of starting work on mobile, continuing on desktop, and seamlessly transitioning between devices using Happy Coder's real-time synchronization.

Workflow Phases

┌─────────────────────────────────────────────────────────────────┐
│                 MOBILE DEVELOPMENT WORKFLOW                     │
├───────────────┬───────────────┬───────────────┬─────────────────┤
│   PHASE 1     │   PHASE 2     │   PHASE 3     │   PHASE 4       │
│   MOBILE      │   TRANSITION  │   DESKTOP     │   REVIEW        │
│   INITIATION  │               │   EXECUTION   │                 │
├───────────────┼───────────────┼───────────────┼─────────────────┤
│ - Describe    │ - Return to   │ - Review code │ - Test changes  │
│   feature     │   desk        │   in IDE      │ - Create PR     │
│ - Plan with   │ - Session     │ - Make edits  │ - Deploy        │
│   Claude      │   continues   │ - Run tests   │                 │
│ - Start       │ - Full        │ - Iterate     │                 │
│   generation  │   context     │   rapidly     │                 │
└───────────────┴───────────────┴───────────────┴─────────────────┘

Phase 1: Mobile Initiation

Location: Away from desk (commute, coffee shop, walking)

Steps

1. Open Happy Coder on your phone

2. Start a new conversation or continue existing session

3. Describe your task naturally:

   • "I want to add a logout button to the user profile"
   • "Fix the race condition in the event handler"
   • "Create a new API endpoint for settings"

4. Enter planning mode with Claude:

   /plan Add dark mode toggle to application settings

5. Approve the plan and let Claude start working

Mobile Best Practices

Do	Don't
Describe features in natural language	Try to do detailed code review
Give high-level direction	Make precise line-by-line edits
Review Claude's approach	Debug complex issues
Queue up multiple tasks	Approve without understanding

Phase 2: Transition

Trigger: Ready to sit at your desk

What Happens Automatically

┌─────────────────────────────────────────────────────────────────┐
│                    SEAMLESS HANDOFF                             │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  Mobile Session                      Desktop Terminal           │
│  ┌─────────────┐                    ┌─────────────┐            │
│  │ Conversation│    SAME SESSION   │ Conversation│            │
│  │ Context     │ ═══════════════▶  │ Context     │            │
│  │ File State  │                   │ File State  │            │
│  │ History     │                   │ History     │            │
│  └─────────────┘                    └─────────────┘            │
│                                                                 │
│  No export. No handoff. No rebuilding context.                 │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

Steps

1. Walk to your desk - Claude keeps working
2. Open terminal - Session is already there
3. Continue immediately - No setup required

Phase 3: Desktop Execution

Location: At your desk with full IDE setup

Steps

1. Review generated code in your IDE
2. Run the test suite:

   npm test

3. Make refinements through Claude or manually
4. Iterate rapidly with full desktop tooling

Desktop Advantages

Capability	Why Desktop Is Better
Multi-file review	See code side-by-side
Debugging	Full debugger access
Testing	Hot reload, watch mode
Git operations	Visual diff tools

Phase 4: Review & Deploy

Steps

1. Final code review with full context
2. Run full test suite
3. Create pull request:

   gh pr create --title "Add logout button" --body "..."

4. Deploy to staging/production

Complete Example

Scenario: Adding User Preferences Feature

7:45 AM - On the train (Mobile)

You: "I want to add a user preferences page that lets users
     set their theme, notification settings, and timezone"

Claude: "I'll create a preferences page. Let me plan this out..."

[Claude enters planning mode, you approve]
[Claude starts generating code]

8:15 AM - Arrive at office (Transition)

[Walk to desk, open terminal]
[Session is already there with progress]

8:20 AM - At desk (Desktop)

You: "Looking good. Let's also add validation for the timezone
     field and make sure the tests cover edge cases"

[Review code in VS Code]
[Run tests, make adjustments]

9:00 AM - Ready to ship

git add .
git commit -m "Add user preferences page"
gh pr create

Success Criteria

• [ ] Task completed with minimal context switching
• [ ] Mobile time used for high-level direction
• [ ] Desktop time used for detailed work
• [ ] Seamless transition with no lost context
• [ ] Tests passing before merge

Related Documents

• SOP-003: Session Management
• SOP-004: Voice Coding
• WF-002: Hemingway Technique