NOTO v1.1.4

Noto for Android, published as an APK you can install from the download page.

1.1.3 shipped the desktop applications but not the Android build: the signing
job refused to run without an upload key, which is what it is supposed to do
rather than publish an APK signed with Android's shared debug key. That key now
exists, so this release carries the APK 1.1.2 and 1.1.3 both promised.

Android

The download page now offers an Android build for phones running Android 7.0
or later. The recommended download is the 64-bit APK, which every phone made
since roughly 2016 wants; a 32-bit build is published alongside it for older
hardware.

It is a 16 MB download. The generated Android project would have made it 104
MB for an application whose JavaScript is 2.2 MB: one APK carrying native code
for four processor architectures, stored uncompressed, three of which no
single phone can run. Each APK now carries one architecture, unreachable code
is stripped from the release build, and the native libraries are compressed.

Noto is not on Google Play yet, so Android asks you to permit the install once
— that prompt is expected for anything from outside the store. Open the file
after it downloads and confirm.

Documents on the phone are stored in on-device SQLite, the same local-first
arrangement as every other platform. There is no account, and no sync: notes
written on the phone stay on the phone for now.

Signed with a real upload key

Every APK here is signed with Noto's upload key rather than the debug key that
ships with the Android SDK and is byte-identical on every machine. That
distinction matters more than "unverified" suggests: anyone can sign an APK
with the debug key, and Android would accept it as a legitimate update to Noto.

The pipeline fails outright when the key is absent instead of falling back to
the debug key, which is exactly what happened on 1.1.3.

Everything from 1.1.3

The desktop applications, the download page that only links files a release
actually carries, and the packaging fixes that stopped a hung build from
cancelling an entire release are all unchanged from 1.1.3. Nothing on the
desktop needs updating for this release.

Known limitations

Unchanged: the desktop installers are unsigned, so Windows SmartScreen and
macOS Gatekeeper warn on first launch — verify your download against
SHA256SUMS.txt. macOS auto-update needs a signed build, and Windows ARM64 is
installer-only. iOS is not published. Cloud sync is not enabled on any
platform.

---

Downloads

Windows

Package	File
Installer (x64)	Noto-1.1.4-win-x64.exe
Installer (ARM64)	Noto-1.1.4-win-arm64.exe

macOS

Package	File
Disk image (Apple Silicon)	Noto-1.1.4-mac-arm64.dmg
Disk image (Intel)	Noto-1.1.4-mac-x64.dmg
Archive (Apple Silicon)	Noto-1.1.4-mac-arm64.zip
Archive (Intel)	Noto-1.1.4-mac-x64.zip

Linux

Package	File
AppImage (x64)	Noto-1.1.4-linux-x64.AppImage
Debian package (x64)	Noto-1.1.4-linux-x64.deb
RPM package (x64)	Noto-1.1.4-linux-x64.rpm

The web application needs no download and is always at the latest version.

---

Verifying a download

Checksums for every asset are published as SHA256SUMS.txt.

sha256sum --check --ignore-missing SHA256SUMS.txt

---

Updating

Windows and macOS installations update themselves: Noto checks for a new version on startup, downloads it in the background, and applies it on the next restart.

On Linux, replace the AppImage or install the new .deb/.rpm through your package manager.

---

System requirements

Platform	Requirements
Windows	Windows 10 or later, x64 or ARM64, 4 GB RAM, 500 MB storage
macOS	A supported modern macOS version, Apple Silicon or Intel, 4 GB RAM, 500 MB storage
Linux	x64, 4 GB RAM, 500 MB storage
Web	A current version of Chrome, Edge, Firefox or Safari

Full details: System requirements

Full Changelog: v1.1.3...v1.1.4