DroppyKit

Submit a Droplet.

You built it with DroppyKit. Send the repository and the commit, and it gets read, built, signed and published to the Store beside your name. The reference comes straight back, on this page and by email.

Send it for review What review looks for

What happens next

Nothing you send is executed before a person has read it. Here is the whole path, in order.

1
It lands in the queue
You get a reference on this page and by email the moment you press send. That reference is how to ask about the submission later.
2
Read and built at your commit
The exact commit is cloned, validated and built, never run. Then the source is read, the way any code that runs inside Droppy is read.
3
A human answers
The decision, or a question, comes from hi@getdroppy.app to the address you give. Most submissions hear back within a few days.
4
Signed and published
An accepted Droplet is built against the framework Droppy ships, signed with Droppy's Developer ID, notarized and listed in the Store beside your name.

Before you send

droppykit validate passes. They are the intake's own checks, so a Droplet that passes locally passes here.
The repository is public and reachable without credentials.
The icon and creator avatar are real artwork, not the scaffold's placeholders.
The commit is the one you want reviewed. droppykit submit fills this form in from your checkout.

Questions before you send? Write to hi@getdroppy.app. An update to a published Droplet is a new submission naming a new commit.

Send it for review

Only what review needs. The reference comes back the moment you press the button.

Repository

The page of the repository, over https. Public, no credentials.

Commit

The full 40-character SHA, from git rev-parse HEAD. This is the commit review clones and builds; droplet.json does not name one.

Droplet id

The id from droplet.json. Lowercase.

Your name

Anything we should know (optional)

droppykit validate passes on this commit, the repository is public, and the icon and creator avatar are my own artwork. I have read what review looks for.

Loading secure verification...

Your email is used to reply about this submission and nothing else. The commit is pinned: a repository that moves afterwards does not change what is reviewed.

✓

It is in the review queue

A human reads it next. The decision, or a question, comes to the address you gave.

ReferenceDS-000000

The same reference is on its way to your inbox. Reply to that email to add anything.

The exact commit is cloned, validated, built and read.
You hear back from hi@getdroppy.app, usually within a few days.
Accepted Droplets are signed, notarized and listed beside your name.

Frequently asked questions

How long does review take?

There is no promised date, but a human opens every submission and most hear back within a few days. The reference you get is how to ask about one; reply to the receipt email and it 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. A submission without a public repository is refused at intake.

Does my licence change?

No. Your licence covers your code 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 repository.

What if review sends it back?

You get the reason by email. Push a fix and submit the new commit; the same reference stays attached. A returned submission is not a rejection, and most that come back once ship on the next commit.

Can I update a published Droplet?

Yes. Raise version in droplet.json, push, and submit the new commit. The Store compares versions to decide who needs the update, so the number has to go up every time.