Desktop App
CodeSCE has a native desktop app (Windows/macOS) alongside the web version. It shares your account and catalog, but is optimized for a local workflow — getting modules from the marketplace into the projects on your machine.
Full reference
This page covers the desktop app from a buyer's point of view. For the complete walkthrough — install, authentication internals, and workflow — see the Desktop App section.
Why use the desktop app
- A native, focused window for browsing, buying, and downloading.
- A smoother local workflow for pulling purchased modules into your projects.
- The same account, purchases, and downloads as the web — nothing is separate.
How it works (system-browser auth)
The desktop app deliberately does not collect your Google or GitHub login inside its own window. Signing in happens in your real browser, where you can trust what you're seeing:
- You start sign-in in the app.
- The app opens the auth pages in your default system browser.
- You authenticate with Google or GitHub there.
- When it's done, your session is handed back to the app via a
codesce://deep link, and you're signed in.
Everything after sign-in — browsing, buying, downloading — happens inside the desktop app itself.
Why open the system browser?
It keeps authentication in a trusted, familiar environment and means the app never handles your provider credentials directly. See Authentication Flow for the details.
Local workflow
Once signed in, the desktop app is built around getting modules onto your machine:
- Buy and download modules just like on the web.
- Handle downloaded files locally, ready to unpack and integrate.
- Move from purchase to project with fewer context switches than the browser.
Next step
That's the buyer journey end to end. To go deeper on any part, jump to Security or the full Desktop App section.