Developer Center - building your own evmux app
Anyone can use the apps and widgets in a scene. The Developer Center is where someone builds their own app for evmux. It lives in the dashboard, not in the studio.
Getting access
The Developer Center is not open to every account. Access is granted by evmux, and the way to ask for it is to contact support, explaining your background and experience and what app you want to build. Approved users then see a Dev center entry in the dashboard profile menu (top right, marked Beta).
If someone cannot see that entry, the answer is to talk to support - not to hunt for a setting, because there is nothing for them to switch on themselves.
The developer documentation
Apps are built with the evmux JavaScript SDK, and its documentation is public:
You can read it before asking for Developer Center access, to see what building an app involves. It covers:
| Section | What it explains |
|---|---|
| About the SDK and Setup | What the SDK is, the npm packages, and how to add them to a project |
| Overview, App Creation, Lifecycle | How an app is structured, how it is created and loaded, and what happens from install to removal |
| Security | The permissions an app declares and how users grant them |
| Health and metrics | How the studio monitors a running app |
| Demo app code (pure JS) | A complete working example to start from |
| Creation, Properties, Events, Methods | The API itself: creating the app object, what it exposes, what it can listen to, and what it can call |
The SDK supports two kinds of app. Widget apps are installed on a stream and appear in the App Market for use as a layer, like the built-in apps described in Apps & Widgets. Dashboard apps are installed on a project or session from the dashboard and work with it there. In both cases the user grants the app’s permissions when installing it.
Who manages to build one
Web developers generally have no trouble - it is ordinary web development against the evmux app API, and the SDK documentation and its demo app cover the rest.
Someone who is not a developer but is comfortable working with coding models (Claude and the like) can also produce a decent app. Be straight about the cost: it takes time and patience, and they may need to pick up the basics of web development on the way. It is realistic, not instant.
What is inside
The Developer Center opens on My apps - your apps listed with their Dev Version and Production Version - plus Create new App. Each app then has its own sections:
App information. The app’s name, a full description (up to 4000 characters) and a short marketing description (up to 47 characters), tags, a YouTube link for a demo video, and the developer’s own details - name, email, website and a link to their Terms of Use.
Widget settings. The permissions the app asks for, its keywords, and how it is placed on a scene by default: starting position and size, width, height, rotation, whether the aspect ratio is locked and whether it adapts.
Versions. Apps are uploaded as a zip archive. There are two slots - the Dev Version you are working on and the Production Version, which is the approved one. That separation is what lets you try a new build without touching what users are running.
Submission and review. Pick the version to submit, say what is new, add a description for the review, and send it. The review’s outcome and any response come back on the same page.
Statistics. Usage figures for the app.
Permissions: ask only for what the app needs
An app declares the permissions it wants, and those are looked at during review. If an app asks for access to everything while plainly needing very little, the submission can be denied, with guidance on what to correct - the same principle as a phone app: a bell-ringer has no business asking for your contacts.
In practice this is rare. Most app developers already know the convention and ask only for what they use. The advice to give is simply: request the narrowest set of permissions the app actually needs, and expect to justify anything unusual.
Publishing
Once an app is built and approved, it can be published so it is visible to all evmux users rather than just its author’s account. Publishing goes through review - it is not instant.
Selling and monetisation
evmux does not allow apps to be sold through evmux, and provides nothing to support sales - no payments, no licensing, no verification that a sale happened.
A developer may try to monetise their app by their own means, but it is entirely their own arrangement and their own responsibility. evmux will not verify sales, resolve disputes, or help with any of it. Say this plainly if asked, and never hint at a marketplace or a revenue share, because there is none.
Answering these
Do not describe evmux as a place to sell apps - publishing makes an app available to everyone, it does not sell it. And do not speculate about how access is granted or who reviews a submission: the honest answer is that access comes through support and submissions are reviewed by evmux.