Turn any book or document into a personalized listening experience for your commute.
Ridecast is a generative audio platform that converts written content into high-quality, AI-narrated audio optimized for car rides and commutes.
This is a spec-driven filesystem for the Ridecast project. All product requirements, design decisions, and technical specifications are documented as markdown files, following the Amplifier methodology.
ridecast/
├── 1-vision/ # High-level vision and goals
│ ├── Vision.md
│ ├── ProblemStatement.md
│ ├── Principles.md
│ └── SuccessMetrics.md
│
├── 2-product/ # Product specifications
│ ├── epics/ # High-level feature epics (Epic 1-5)
│ ├── features/ # Detailed feature specs (Feature 1.1, 2.1, etc.)
│ │ ├── epic-1-audio-creation/
│ │ ├── epic-2-voice-system/
│ │ ├── epic-3-library-playback/
│ │ ├── epic-4-user-profiles/
│ │ └── epic-5-car-mode/
│ └── userstories/ # User stories (US 1.1.1, 1.1.2, etc.)
│ └── epic-{name}/feature-{x.y}/
│
├── 3-design/ # Design documentation
│ ├── DesignVision.md
│ ├── InteractionFlow.md
│ ├── CarModeUI.md
│ ├── VoiceSelectionUI.md
│ └── PrototypeLinks.md
│
├── 4-technology/ # Technical architecture
│ ├── Architecture.md
│ ├── StackDecisionLog.md
│ └── DataFlowDiagram.md
│
├── amplifier/ # Symlink to ~/dev/toolkits/amplifier
├── templates/ # Symlink to ~/dev/toolkits/templates
└── README.md # This file
Mission: Make knowledge accessible and engaging during drive time by creating high-quality, AI-generated audio content that adapts to your preferences, schedule, and listening context.
Core Value:
- Turn reading time into drive time
- Personalized audio experience
- Commute-optimized content
- Offline-first architecture
- Hands-free, safety-first controls
- Audio Creation: Convert EPUB, PDF, TXT, and URLs to audio
- Voice Selection: Choose from multiple high-quality AI voices
- Library & Playback: Organize and play audio content offline
- Car Mode: Safety-focused UI with large controls and voice commands
- Cross-Device Sync: Resume seamlessly across devices
- CarPlay and Android Auto integration
- Custom voice cloning
- Smart playlists based on commute length
- Multi-language support
- Social features (shared playlists)
- Vision - Full product vision and long-term goals
- Problem Statement - The problem we're solving
- Design Principles - Core principles guiding decisions
- Success Metrics - How we measure success
- Epics - High-level feature groups (Epic 1-5)
- Epic 1: Audio Creation
- Epic 2: Voice System
- Epic 3: Library & Playback
- Epic 4: User Profiles
- Epic 5: Car Mode
- Features - Detailed feature specs (Feature 1.1, 2.1, 3.1, 3.2, 4.1, 5.1)
- User Stories - Stories with acceptance criteria (US 1.1.1, 1.1.2, etc.)
- Design Vision - Visual and interaction design philosophy
- Interaction Flow - User flows and journeys
- Car Mode UI - Driving-optimized interface
- Voice Selection UI - Voice browsing and preview
- Prototype Links - Links to Figma/mockups
- Architecture - System architecture overview
- Stack Decision Log - Technology choices and rationale
- Data Flow Diagram - How data moves through the system
- iOS: SwiftUI, AVFoundation, CarPlay
- Android: Jetpack Compose, ExoPlayer, Android Auto
- API: Node.js (Express) with TypeScript
- Database: PostgreSQL
- Cache: Redis
- Storage: AWS S3 or Google Cloud Storage
- Queue: Redis Queue or AWS SQS
- TTS API: Azure Neural TTS or ElevenLabs
- CDN: CloudFlare or AWS CloudFront
- Auth: JWT with refresh tokens
- Analytics: Mixpanel or Amplitude
- Error Tracking: Sentry
This project follows a spec-driven development approach:
- Define: Write specs before building features
- Review: Collaborate on specs via PRs
- Build: Implement against approved specs
- Iterate: Update specs as we learn
All spec documents include frontmatter:
---
version: 0.1.0
author: Chris Park
status: draft | in-review | approved | implemented
last_updated: 2025-10-10
type: vision | product | design | technical
---Phase: Initial Planning & Spec Development
- Project structure created
- Vision documents drafted
- Product epics defined
- User stories written
- Design principles established
- Technical architecture drafted
- Technology decisions finalized
- Prototypes created
- MVP development started
This is currently a solo project by Chris Park. If you're interested in contributing or collaborating, please reach out.
- Start with Vision: Read Vision.md to understand the big picture
- Explore Product: Check Epics to see planned features
- Review Design: Look at Design Vision for UX principles
- Understand Tech: Read Architecture.md for technical details
TBD - This is currently a private project.
Chris Park
- Project: Ridecast
- Methodology: Amplifier (spec-driven development)
| Version | Date | Changes |
|---|---|---|
| 0.1.0 | 2025-10-10 | Initial project structure and specs |
- Inspired by the need for productive commute time
- Built with the Amplifier spec-driven methodology
- Using Claude Code for project initialization
Note: This is a living document. As the project evolves, this README will be updated to reflect current status and progress.