DroppyKit

Publish a Droplet.

You built it with DroppyKit. The Store is a repository, one folder per Droplet: open a merge request that adds yours, and once it merges the pipeline builds it, signs it and puts it on every Mac's shelf beside your name. No form, no waiting for a build.

Open the Store repository What review looks for

How it works

Every Droplet in the Store lives in gitlab.com/droppyformac1/droplets, under droplets/<id>/. Merging is publishing.

1
Open a merge request
droppykit submit forks the repository once, copies your package into droplets/<id>/, pushes a branch and opens the merge request with the checklist filled in. Or do the same by hand.
2
The pipeline checks it
The moment the merge request opens: the manifest, the folder, the avatar, the changelog entry, the version bump, the dependencies. Every rule is written down in the repository's CONTRIBUTING.md, so nothing comes back for a rule you could not have known.
3
A human reads it
A Droplet is native code inside Droppy's process, so a maintainer reads the source before merging. Questions come as comments on the merge request; a new commit on the same branch answers them. Jordy also makes the Droplet's icon and adds it before it publishes.
4
Merged means published
The pipeline on main builds it universal, signs it with Droppy's Developer ID and writes it to the Store's catalog. Every Mac running Droppy can install it within minutes, and the Source code button on its page opens your folder.

Before you open it

droppykit validate passes. They are the repository's own checks.
CHANGELOG.md starts with an entry for the version in droplet.json; it becomes the update's release notes.
The creator avatar is real artwork, not the scaffold's placeholder.
No icon of your own: Jordy designs every Droplet's icon. Add an idea for it in the merge request if you have one.
capabilities lists what the Droplet uses and nothing else.
You have read the Droplet developer terms: the Droplet, its bugs and how it treats people's data are yours.

An update is the same thing again: raise version, add the changelog entry, open a merge request. Questions before you open one? The Trench, or hi@getdroppy.app.

Three commands

From the folder of a Droplet that builds. glab is GitLab's command line; sign in once.

# once brew install glab && glab auth login # in your droplet's folder droppykit validate droppykit submit

submit writes your folder's Store page into source.repository and your GitLab username into creator.gitlab, which is what puts you in CODEOWNERS and gets you asked before anyone else changes your Droplet.

Read the guide

Opening the merge request means accepting the Droplet developer terms (version 2026-09-17); the template asks you to confirm it.

Frequently asked questions

How long does review take?

There is no promised date, but a maintainer reads every merge request and most hear back within a few days. The merge request is where the conversation happens; a comment there reaches the reviewer.

Why does it have to be open source?

A Droplet is native code inside Droppy's process, with Droppy's permissions. That is what lets it draw real SwiftUI on the notch, and the price of it is review, which means readable code. The Store repository is public, and what merges there is what ships.

Do I make the icon?

No. Jordy designs every Droplet's icon himself, in Icon Composer and in Droppy's own style, so it adapts to light, dark, clear and tinted icons and sits right beside the rest of the Store. droppykit submit leaves the scaffold's placeholder out. If you have an idea for the icon, describe it in the merge request's Icon concept section: a sentence, a sketch, or an SF Symbol to start from. He adds the icon before your Droplet publishes.

Does my licence change?

No. Your licence covers your code (name it in droplet.json under source.license) and the SDK's licence covers the SDK. Publishing to the Store claims nothing over what you built; the Store lists it beside your name and links to your folder.

What if review asks for changes?

The reason is a comment on the merge request. Push a fix to the same branch and the pipeline runs again. A question is not a rejection, and most merge requests that get one merge on the next commit.

Can I update a published Droplet?

Yes. Raise version in droplet.json, add the entry to CHANGELOG.md, and open a merge request. The Store compares versions to decide who needs the update, so the number has to go up every time, and the changelog entry is what the Update button shows.