Using a Module

You've bought a module and downloaded it. Here's how to go from a ZIP file to a working piece of your app.

1. Download the ZIP

Download delivers the module's source as a ZIP archive. Each ZIP is watermarked to you, the buyer — an embedded, per-purchase marker that ties the copy to your account. It doesn't change how the code runs; it's there for traceability if a paid module is ever leaked.

Keep it to yourself

Because the ZIP is watermarked to your account, redistributing it can be traced back to you. Treat it as your licensed copy.

2. Open the UI / preview

Unpack the ZIP and open the module's UI to see it running locally — the same interface you saw in the marketplace preview. Use it to confirm the module behaves as expected before wiring it in.

3. Configure via the dynamic form

Modules are designed to be configured without editing source code. Each one ships with a config schema that CodeSCE renders as a form using the Dynamic Form Engine. You fill in the module's variables — labels, options, toggles, and values the author exposed — and the module picks up your settings.

This is the same set of config options you saw on the module page before buying. For how the schema and form engine work, see Dynamic Configuration.

4. Integrate into your project

With the module configured, drop it into your codebase:

1. Add the files from the ZIP into your project.
2. Apply your configuration from the form.
3. Wire it into your app following the module's README, which documents its integration steps and any requirements.

Because modules are built to be plug‑and‑play, integration is mostly copying in the files, setting your config, and calling the module where you need it. See the Integration Model for the general pattern.

Next step

Want the smoothest local workflow for this? Try the Desktop App →.