Product roadmap
First, make the core app work. Then expand into the tools builders already use. Later, explore a mobile companion if the launch queue proves useful enough to follow people away from the desk. This is product direction, not a promise about exact timing, packaging, or pricing.
V1.0
The short-term goal is simple: make TryLaunchLoop reliably turn shipped product work into useful posts. That means basic GitHub ingestion, enough project context to understand what changed, and a review flow where a builder can approve, edit, copy, and publish without fighting the tool.
V2.0
The next version is the bigger automation layer: cloud Codex workflows, Codex plugins, Claude skills, CLI support, publishing to more channels such as Facebook and Threads, image and video generation, richer integrations, and deeper scheduling automation once the approval loop is trustworthy. This is where the larger long-term package belongs, after the core app proves it can consistently create good launch material.
V3.0
A later direction could be an iOS app for reviewing launches away from the desk: approving drafts, checking scheduled posts, and keeping the launch queue moving from a phone. That is intentionally farther out; the core workflow comes first.
