Publishing
Take a Lens from Lens Studio to SPECS users: upload an SPK, list it, pass review, and release it.
You can release to your organization, to beta testers, or to everyone in Lens Explorer.
How publishing works
| Step | What you do | Where |
|---|---|---|
| 1 | Create the Lens and claim its package ID | Lens Studio or the portal |
| 2 | Upload an SPK (a signed .spk) | Lens Studio or the portal |
| 3 | Write the store listing and add preview media | Portal |
| 4 | Rate content and declare data use | Portal |
| 5 | Submit for review | Portal or API |
| 6 | Release to a channel | Portal or API |
| 7 | Ship updates | Portal |
Key terms
- Lens — the product a SPECS user installs. A Lens has one package ID, one store presence, and many releases.
- Package ID — the permanent, globally unique ID of a Lens, such as
com.example.periodic_table. It is set in Lens Studio and cannot be changed or reused. - SPK — a SnapOS Package: the signed package file Lens Studio exports. Every SPK has a build version that must increase with each release.
- Release — an SPK plus its store listing, submitted to a channel. Each release has its own release version (
X.Y.Z). - Channel — who receives a release: Organization only, Beta, or Public.
Before you start
- A SPECS Developer Portal account and an organization.
- Lens Studio 5.25 or later, with a SPECS project.
- The production signing key you will use for every release of this Lens. Losing it can prevent future updates.
- For Lenses that sell items or subscriptions, payments set up before you submit.