Tweaks

Publish your own

A Folio source is static files on a web server. No account, no review queue, and nothing to ask me for.

What a package is

JSON and images, plus an optional sandboxed script. A manifest.json says what it is, which screens it supports and the lowest Folio version it needs. A depiction.json is its page in the Market: what it does, what it changes, screenshots and a changelog. Folio builds the privacy label itself, from what the package actually asks for rather than from anything its author wrote.

Making one

1. Copy the Cabinet sample in docs/sdk, which is a working package.
2. Edit the manifest and the depiction, and swap the icon and screenshots.
3. Run folio-pkg validate over it. It catches the mistakes that would otherwise fail on a phone.
4. Sign it with your own key. Folio checks the signature of the package itself, not just the source serving it, so a mirror can carry your work but cannot change it.

Serving it

A source is an index.json and the package folders beside it, on any HTTPS address. GitHub Pages works and costs nothing. Folio shows your source's key fingerprint before anyone trusts it, remembers it, and says plainly if it ever changes.

Anyone adds it in Market › Sources, or by opening a folio://source/ link. A package file sent directly carries its own signature too.

What Folio will not accept

• A package that is not signed, or whose signature does not match its source's key.
• A package using a com.mccal.folio.* name from anywhere but Folio's own sources.
• Anything applied halfway: a package that fails partway through is put back the way it was.

The full format, the sample and the validator are inthe SDK folder. Open an issue if something there is wrong or missing.