Read, discover, and publish Standard.site writing

Not yet. Inkwell installs from its own self-hosted AltStore source (iOS) or F-Droid repository (Android). The download section includes the planned £5 App Store and Google Play routes too, but those buttons currently use placeholder listing URLs until the real store pages exist. AltStore Classic and F-Droid remain the free install routes.

No. Inkwell needs an AT Protocol account and a PDS, not specifically an account hosted by Bluesky. A Bluesky-hosted account works, but so does an account on another compatible PDS or one you self-host. You sign in with your AT Protocol handle through OAuth.

Inkwell reads and publishes Markpub Markdown, Leaflet, pckt, and Offprint content. It renders those formats natively and keeps portable textContent available as a fallback when a client does not understand the richer body format. See Features for the format-by-format detail.

Yes. Inkwell can open existing documents for editing and publish an updated revision back to your repository. If you choose to convert a document between formats, the editor reports content that cannot round-trip cleanly before you publish the conversion.

Nothing happens to it — your documents are AT Protocol records in your own repository on your PDS, not data stored by Inkwell. Any client that speaks the Standard.site record schemas can read or edit them, with or without Inkwell.

No. Inkwell reads and writes your content directly on your PDS and has no intermediary database of your documents. Your OAuth session and DPoP key are stored on your device in the platform's secure storage; the app contains no analytics or tracking SDK. See Security and Privacy for the full detail.

No. You'll need an AT Protocol account and a PDS to sign in with — Inkwell doesn't create one for you — but from there it works like any reading and writing app. See About if you'd like the background.

Inkwell does not send your subscriptions to a push-notification service. The app periodically checks the publications you follow and creates local notifications on your device when it finds new documents. You can turn the OS banners off without losing the in-app notification history.

Yes. Sign in to the same AT Protocol account and both apps read the same repository-backed publications, documents, subscriptions, and recommendations from your PDS. Device-local preferences such as appearance, accessibility, and notification settings are configured separately on each device.

The iOS app supports iOS 18 and later. The Android app supports Android 8.0 (API 26) and later, and currently targets Android API 36.

Yes, for normal use. Android now covers the core Inkwell experience: reading and discovery, publishing and editing across the supported Standard.site formats, comments and interactions, subscriptions and recommendations, verification, notifications, settings, and accessibility and customisation controls. It is still labelled experimental because its Android-specific automated coverage is comparatively thin and iOS remains the primary, more polished implementation.

A publication or document can claim a canonical web address, but a claim alone isn't proof. Inkwell checks that claim against the site's .well-known endpoint and its canonical <link> tag, surfacing a mismatch instead of silently trusting it. More detail on Security.