ilia/atlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
atlas/tickets/backlog/TICKET-039_phone-client-pwa.md
ilia 7c633a02ed Initialize project structure with essential files and documentation 
- Added .cursorrules for project guidelines and context
- Created README.md for project overview and goals
- Established ARCHITECTURE.md for architectural documentation
- Set up tickets directory with initial ticket management files
- Included .gitignore to manage ignored files and directories

This commit lays the foundation for the Atlas project, ensuring a clear structure for development and collaboration.
2026-01-05 20:09:44 -05:00

1.4 KiB
Raw Blame History

Ticket: Phone-Friendly Client (PWA or Native)

Ticket Information

  • ID: TICKET-039
  • Title: Phone-Friendly Client (PWA or Native)
  • Type: Feature
  • Priority: High
  • Status: Backlog
  • Track: Clients/UI
  • Milestone: Milestone 2 - Voice Chat MVP
  • Created: 2024-01-XX

Description

Build phone-friendly client:

  • Decide PWA vs native (PWA likely: microphone access, push notifications, WebSocket)
  • Voice capture UI (tap-to-talk + optional wake-word)
  • Stream audio to ASR endpoint
  • Conversation view (history, agent responses, tasks created)
  • Text + play/pause TTS

Acceptance Criteria

  • PWA or native app decision made
  • Voice capture UI implemented
  • Audio streaming to ASR working
  • Conversation view implemented
  • TTS playback working
  • Task display working

Technical Details

PWA approach:

  • Service worker for offline support
  • WebSocket for real-time communication
  • getUserMedia for microphone access
  • Push notifications for reminders/timers

Features:

  • Tap-to-talk button
  • Wake-word option (if browser supports)
  • Conversation history
  • Audio playback controls
  • Task list view

Dependencies

  • TICKET-010 (ASR endpoint)
  • TICKET-014 (TTS service)
  • Can be mocked early for UI development

Related Files

  • home-voice-agent/clients/phone/ (to be created)

Notes

Independent of MCP tools - only needs chat endpoint to start. Can begin with mocks.