Topicle for Android: direct download

Download

Version 1.4.5-direct (build 23).

topicle-1.4.5-direct.apk

topicle-latest.apk is the same file under a stable name, always pointing at the newest release.

APK SHA-256

Signing certificate SHA-256

This is the value to compare against what apksigner verify --print-certs prints for the file you downloaded. It is the same on every release, so a change here without an announcement is a reason to stop and ask.

Not what you were after?

Google Play remains the primary way to install Topicle on Android. This build exists for people who want a phone without Google services on it.

Verify what you downloaded

Two commands, both on the downloaded file. The first prints the APK checksum, which should match the SHA-256 above:

sha256sum topicle-1.4.5-direct.apk

The second prints the certificate the APK is signed with. Its SHA-256 digest should match the signing certificate fingerprint above:

apksigner verify --print-certs topicle-1.4.5-direct.apk

If either value does not match, do not install the file.

Getting the tools

On macOS, sha256sum is called shasum -a 256. On Windows, certutil -hashfile topicle-1.4.5-direct.apk SHA256 prints the same value.

apksigner is not installed by default anywhere; it ships with the Android SDK build tools. If you have Android Studio, open SDK Manager, SDK Tools, and install Android SDK Build-Tools; the binary is then at <sdk>/build-tools/<version>/apksigner (the SDK is ~/Library/Android/sdk on macOS and %LOCALAPPDATA%\Android\Sdk on Windows). Without Android Studio: Debian and Ubuntu have apt install apksigner; on macOS, brew install --cask android-commandlinetools then sdkmanager --install "build-tools;36.0.0" puts it under /opt/homebrew/share/android-commandlinetools/build-tools/36.0.0/.

What is and is not in this build

The precise claim, because this audience checks: no Google Play Services, no Firebase, no proprietary Google components. Not "no Google code at all". The UnifiedPush connector that delivers notifications depends on Tink, a cryptography library published by Google under the Apache 2.0 licence, so the stronger claim would be false.

Permissions: this build requests WAKE_LOCK, which the UnifiedPush connector uses to receive notifications while the device is idle. It does not request the Firebase Cloud Messaging or Play Install Referrer permissions that the Play build carries, both of which bind to Google Play services. It also declares REQUEST_INSTALL_PACKAGES, Android's "install unknown apps" permission. The app uses it only to install Topicle's own updates from this page, only after you agree, and you can turn it off in Android settings at any time.

Where is the source? The source code is not published at this time.

Notifications

Notifications arrive over UnifiedPush. Install a distributor, for example ntfy, open it once after installing it (Android does not deliver the registration to an app that has never been opened), then pick it in the app's notification settings. Without a distributor, everything else in the app works and notifications are simply off.

Notification payloads are encrypted end to end between Topicle and your device, so the distributor, including one you host yourself, cannot read them.

Updates

The app checks for a newer version when it starts, and again when you come back to it after a few hours, and shows a small banner at the top of your home feed when there is one. Choosing Later puts it away for a few days, and each Later after that waits longer, up to a month.

Updating opens the APK from this page in your browser and Android's installer does the rest. The app can also install the update for you in one tap. It asks before it uses Android's "install unknown apps" permission, checks the downloaded file against the checksum and signing certificate published on this page (see Verify what you downloaded), and Android shows its own confirmation every time. You can decline it and keep using the browser, or turn it off later in Android settings.

If you would rather automate that, Obtainium can track this page: it reads the HTML, finds the versioned APK link, and tells you when the version changes. Add Topicle to Obtainium opens Obtainium with the configuration filled in, and shows it to you before anything is added.

By hand instead: add https://topicle.com/downloads/android with the source set to HTML, and set the APK filter to topicle-.*-direct\.apk$. Obtainium reads this page only; the app's own version feed is a separate thing and Obtainium does not use it.

Switching between Google Play and this build

Both builds use the same package name but are signed with different keys, so Android will not upgrade one into the other. Switching means uninstalling the one you have and installing the other. That is how Android package signing works and it is not something we can smooth over.

Your account, posts, comments, saved items, and subscriptions live on the server, so none of that is affected. Check your notification settings after switching: the two builds deliver notifications by different routes, so the setting does not carry across.

Signing in without Google

Google sign-in is not part of this build. If you created your account with Google, use "Forgot password" once with your account email address to set a password, then sign in with your email address and that password. Password manager autofill works normally.