Local Workflow
Once you're signed in, the desktop app is the same CodeSCE experience in a native window — plus a workflow built around getting modules onto your machine and into your projects.
Everything happens in the app
Because the content window runs the full CodeSCE web app against the real backend, everything you do on the web works here too, inside one window:
- Browse the marketplace.
- Buy modules (payment flow is identical).
- Download purchased modules.
- Manage your purchases and profile.
Only the authentication pages ever leave the app (to your system browser); the rest is native.
Download handling
Downloads in the desktop app use the exact same secure delivery as the web:
- Each download is fetched through a short-lived, one-time, signed link tied to your account.
- The delivered ZIP is watermarked to you.
- The app saves the file locally, ready to unpack — right where you'll integrate it.
There's no separate "download store" to manage: you own the module permanently, and you can request a fresh, secure copy whenever you need one.
Integration flow
From a downloaded module, the path into your project is the standard one:
- Unpack the watermarked ZIP into your project.
- Preview the module's UI to confirm it behaves as expected.
- Configure it through its dynamic form.
- Wire it in following the module's README.
- Verify it runs in place with your settings.
See the Integration Model for the general pattern and Using a Module for the buyer walkthrough.
Behind the scenes
When the app connects to a backend, it waits until that backend reports healthy before loading the interface — so you don't land on a "connection refused" screen during startup. In production this is CodeSCE's cloud backend; in a local development setup the app can run one on your machine. As a user, you just see the app come up ready to go.
That's the desktop app
Sign in once through your browser, then browse, buy, download, and integrate — all from a single native window. Next, see how the whole system fits together in Architecture.