macOS
Signed · notarisedtwriter is signed with an Apple Developer ID and notarised by Apple.
The build train that ships twriter: signed, notarised, and updated in place.
Before the first release
twriter is being packaged for its first release, so there is no download on this page yet. It will be free on macOS and Windows: your manuscript and your canon in one place, with a linter that catches the moment chapter 15 contradicts chapter 3. Join the beta list and you will hear the day there is a build to install.
The rest of this page is written for that day: what twriter needs from your machine, what the first launch looks like on each platform, and how to check a download against its published checksum.
Every platform, every architecture.
No builds published yet.
When the first release ships, every build appears here with its size and its checksum.
Here is exactly what each platform will show you the first time you run it.
twriter is signed with an Apple Developer ID and notarised by Apple.
The Windows build is not signed with an Authenticode certificate, so SmartScreen will show a “Windows protected your PC” warning before it will run. Choose More info → Run anyway.
Every build's SHA-512 is listed in the table above. Checksums are published as base64, matching the update feed exactly.
The obvious command is the wrong one: shasum -a 512 prints hex and will never match. Use the two-stage pipe.
openssl dgst -sha512 -binary twriter-<version>-<arch>.dmg | openssl base64 -A
Shown for reference. There is no published file to check yet. The filename will follow this shape.
twriter checks for updates when it starts, downloads them in the background, and installs them the next time it opens. Updates come from twriter.sh, not an app store.