ready now
Web first
The browser application is already the main product and the fastest path to early users.
Desktop preview
Treat the desktop download as the next layer around the app, not the starting burden.
This page belongs on the website because it explains where ClastX goes next. The actual coding experience still belongs inside the web application until desktop adds something meaningfully better.
shape next
Mac app
Wrap the web workflow into a desktop shell when file access, repo workflows, and billing start to make sense.
later after traction
Windows app
Keep this in the expansion path after the web product and Mac route have proven demand.
What matters before a download exists
The browser workflow should already feel desktop-worthy before you wrap it.
Saved context, better file flows, and billing make the desktop story easier to justify.
Desktop should expand the product, not distract from proving the core web experience.
Where to focus now