ProductRoadmapGrowth
Growth Roadmap
Próx OS should grow through concrete demos and visible user-created spaces, not a vague platform pitch.
Próx OS should grow through concrete demos and visible user-created spaces, not a vague platform pitch.
The early narrative:
Paste an awesome GitHub repo. Get a living OS Space.Wave 1 - Build In Public
Goal: help developers and early users understand the product as it evolves.
Operating rhythm:
- Post a 15-45 second demo every 1-2 days.
- Publish one longer thread each week.
- Give each app a small standalone video.
- Explain one pain point per post.
- Prefer real screen recordings over generic AI promotional videos.
Example themes:
- "I turned a GitHub awesome README into a living OS app."
- "I turned a GitHub awesome README into a living OS Space."
- "From RSS chaos to a personal knowledge inbox."
- "Building a cloud-first personal intelligence OS."
- "Why iframe is only the first integration layer."
Founder-Led YouTube Live Build Loop
Goal: make the founder's live building process itself a retention surface. Próx OS should not only be shown after releases; it should be the operating room where the product is continuously built in public.
Format:
- Stream regular YouTube sessions where the founder personally vibe-codes new apps, connector surfaces, shell UX, docs, and backend integrations.
- Keep the stream centered on the real OS Shell instead of static slides: app windows, Dock, App Store, docs, roadmap, feedback, tasks, and plugin panels should be visible inside Próx OS.
- Build many small apps live, then graduate the useful ones into registry entries, docs, templates, or App Store collections.
- Show backend connections only when they are safe and permissioned: OAuth, provider adapters, worker routes, analytics, notifications, and MCP tools should be narrated as explicit integration boundaries.
- Let viewers see feedback loops in the OS: issues, comments, plugin outputs, agent results, roadmap cards, and app QA notes should become visible shell surfaces instead of disappearing into separate tools.
- Save every stream as an artifact: video chapters, changelog notes, demo clips, docs updates, follow-up tasks, and a "built live" tag for apps touched during the session.
Retention logic:
| Loop | Retention effect |
|---|---|
| Live app incubation | Viewers return to watch rough ideas become real OS apps over multiple sessions. |
| Visible feedback ingestion | Users see comments and plugin feedback become product changes inside the OS. |
| Backend connection episodes | The platform feels increasingly real as mock apps graduate into live connectors. |
| App backlog continuity | Each stream ends with the next app or integration already queued in the OS. |
| Community co-building | Contributors can suggest apps, data sources, docs, and UI polish during streams. |
Operating principles:
- Prefer honest live iteration over polished demo theater.
- Keep secrets, production credentials, private customer data, and provider tokens out of the stream.
- Use the stream to teach the architecture: App Registry, manifests, route groups, connector permissions, Alma, MCP Gateway, and docs taxonomy.
- Convert repeated live questions into docs, onboarding cards, or App Store detail copy.
- Treat YouTube as a product surface, not only a marketing channel: the stream should make people want to come back because the OS itself keeps evolving.
Wave 2 - Launch One Killer Demo
Goal: launch a concrete sample app instead of the abstract OS.
Priority demo: Awesome GitHub Radar.
Demo angle:
- Input an awesome repo URL.
- Automatically parse the README.
- Structure project entries.
- Show stars, license, language, and last update.
- Add AI summary.
- Add RSS / release monitoring later.
- Save the radar into Próx OS.
Wave 3 - Open Templates And Clone
Goal: create product-led distribution inside the product.
Capabilities:
- Install App.
- Clone as Space.
- Create your own Awesome App.
- Publish Space.
- Made with Prox OS badge.
- Community Gallery.
Viral Mechanics
| Mechanism | Purpose |
|---|---|
| Public Space | Users create public spaces for projects, awesome lists, AI tool radars, cloud dashboards, and learning hubs. |
| Clone / Remix | Other users copy a Space and replace it with their own sources. |
| Badge | Every public Space can show a subtle Built with Prox OS badge. |
| App Template | Awesome List Template, RSS Radar Template, Cloud Dashboard Template, AI Context Template, Personal Home Template. |
| Community Gallery | Featured Spaces, Developer Spaces, AI Tool Radars, Learning Hubs, Cloud Dashboards. |
Launch Priority
- Awesome GitHub Radar.
- RSS Knowledge Inbox.
- AI Context Builder.
These demos map directly to the cloud-first, GitHub-first, RSS-first, and AI Context-first positioning.
Five Example Spaces
Build five high-quality example Spaces before a broad launch:
- AI tools radar.
- Cloudflare tools radar.
- React UI / design systems radar.
- Open source alternatives radar.
- Self-hosted tools radar.
Each should be planned as clone/remix-ready, even if early buttons are concept
or preview states. Each public example should eventually carry a Built with Prox OS badge.
Founder-Friendly Growth Route
The full platform vision is large, but the early loop must be small:
Web OS Shell + Awesome GitHub Radar + Space/Profile concept + Prox Studio prototype + GitHub-backed publishing direction.Execution:
- Stabilize the OS Shell: window manager, dock, app registry, iframe apps, docs, pricing, and Hola.
- Build Awesome GitHub Radar: input repo URL, parse README, structure table, fetch stars/license/language/last update/category, add AI summary, generate Space draft.
- Preview Space/Profile: README, Apps, Sources, cards, AI Context placeholder, pinned Spaces, links, and activity placeholder.
- Prototype Prox Studio: Awesome GitHub Radar, RSS Knowledge Inbox, and Link Dashboard templates; output manifest, README, and Space draft.
- Document and test GitHub-backed publishing: repo template, Cloudflare Pages or Vercel deploy, URL registration, metadata, Profile, star/watch.
- Add Connector/Permission/MCP gradually: read-only first, GitHub + RSS first, MCP-ready manifest first, Gateway later.
Early Channels
- X / Twitter: short demos, threads, build logs.
- GitHub: template repository, issues, README, example Spaces.
- Hacker News / Reddit / Indie Hackers: wait until a playable demo exists.
- Product Hunt: wait for a usable Space/Studio demo.
Avoid These Traps
- Do not build the full social network now.
- Do not build the full App Store now.
- Do not connect ten OAuth providers now.
- Do not build the local client now.
- Do not build the full MCP platform now.
- Do not promise unlimited AI, unlimited hosting, or unlimited MCP calls.
- Do not let Prox OS become an advanced bookmark page.
- Do not use the grand vision as a substitute for the concrete demo.
First $10K Growth Experiment
Two routes should run in parallel:
| Route | Advantage | Risk | Best stage |
|---|---|---|---|
| High-ticket Concierge | Fast cash, real customer learning, high-value validation. | Founder time, agency drift, lower scale. | Demo exists but platform is not mature. |
| Low-ticket Product-led | More scalable, closer to platform dream, self-serve growth. | Slower revenue, needs killer app, traffic, and templates. | Demo has distribution and templates are usable. |
High-ticket offer:
Prox Space Launch Pack
I turn your GitHub repos, awesome lists, docs, RSS feeds, and AI context into a beautiful OS Space.First $10K examples:
- 5 customers x
$2,000. - 3 customers x
$2,000+ 10 Founding Builders x$399. - 2 deep consulting customers x
$5,000.
Every concierge delivery must become a template, doc, Prox Studio capability, or reusable Space pattern.