Welcome to the Ottoverse
Small apps, big questions.
Cook, transcribe, discover music—while learning what AI apps really want to be.
Click any card to see what's inside
Cook with Otto
Client-SideBrowser-native agent. Users log in and supply their own API key—keeping the operational surface tiny while enabling real agentic flows.
Click to see architecture details
Cook with Otto
A purely client-side app demonstrating a surprisingly powerful pattern: front-end agents with user-provided API keys. This keeps infrastructure simple while still enabling sophisticated AI interactions. Firebase for auth and state, AI in the browser.
Technology Stack:
Storytime with Otto
Client-SideMultimodal storytelling environment. Speech, pictures, and drawing as part of the interface—where front-end AI shines.
Click to see architecture details
Storytime with Otto
This isn't just 'generate a story.' It's a creative environment involving multiple input and output modalities. The browser gives you so many inputs for free: speech, images, drawing, instant feedback loops. The model isn't the product—the interaction is.
Technology Stack:
Tunes with Otto
Client-SideMusic discovery and playlist generation exploring client-side AI with external API integration patterns.
Click to see architecture details
Tunes with Otto
Your AI music companion demonstrating how client-side agents can orchestrate external APIs. Create playlists, discover music, all from the browser with smart AI guidance.
Technology Stack:
News with Otto
Backend-DrivenThe 'AI factory' model. Backend runs on schedule, searches per topic, uses agents to craft stories, stores in SQL.
Click to see architecture details
News with Otto
Built around a stateless-ish backend workflow: periodically search → run multiple agents to craft news stories → store in database → frontend reads and displays. This pattern is more predictable and reproducible than triggering expensive AI on every user click.
Technology Stack:
Ottit
HybridHybrid: client + server AI. Interactive feed where some intelligence lives client-side, some on the server.
Click to see architecture details
Ottit
A feed-style app exploring the hybrid pattern. Client-side AI for responsiveness, server-side for secrets and heavy tool use. This is the most complicated category—you pay in duplicated logic, complex auth, and multiple security models. Only justified when benefits outweigh the complexity tax.
Technology Stack:
FreeScribe
Real-TimeReal-time audio streaming with WebSockets. The timing problem: when do you commit based on incomplete input?
Click to see architecture details
FreeScribe
Real-time forces you to care about things demos ignore: latency, partial results, reconnection, graceful degradation. With continuous audio, you often don't know when the user is 'done.' The app needs two brains: streaming brain (draft mode) and commit brain (final actions).