How fatec420/gemini-playground works
Client-Side (Frontend)
• Static Assets (HTML, CSS)
• Core JavaScript Modules
• Audio Processing Components
• Video Processing Components
• WebSocket Client
• Tool Management System
Server-Side
• Deno Server
• Cloudflare Worker
• API Proxy Layer
External Services
• Google Gemini API
• Optional integrations (ChatBox, Cursor)
Top Level (User Interface)
• Video/Audio Controls
• Chat Interface
• Tool Panel
Middle Level (Processing Layer)
• Audio Processing Worklets
• Video Management System
• WebSocket Communication
• Tool Manager
Bottom Level (Backend Services)
• API proxy architecture:
• Format Conversion Layer (Gemini to OpenAI)
• Authentication Handling
• Request/Response Flow
Use the following visual elements:
• Blue: Frontend components
• Green: Processing components
• Orange: API proxy layer
• Purple: External services
Grouping
• Use containers to group related components
• Separate client and server sides clearly
• Deployment options in parallel
Special Considerations:
Audio/Video Pipeline
• Detail the flow from input devices through worklets to the API
• Relationship between recorders and processors
Tool System
• How tools (weather, Google search) integrate with the main application
• Extensibility points
API Proxy
• Demonstrate the transformation of Gemini API format to OpenAI format
• Authentication flow
Deployment Options
• Both Deno and Cloudflare Worker paths
• How they interact with the frontend differently
Labels and Documentation:
Notes for
• API key requirements
• Deployment-specific configurations
• Network routing considerations
Level of Detail:
• Keep high-level components visible at first glance
• Use expandable sections for detailed components
• Version/model information for external services
• Error handling pathways