Skip to content
Google Play release

Google Play release

PULSE ships to phones through Google Play only, published by the Runink organization developer account (one account for every Runink app). This page lists every step from source to the internal testing track. Each step says whether the code does it (code, with where) or the owner does it (owner). Sources, read 2026-11-02:

1. The release build: code

StepStatusWhere
Application id org.runink.pulse (it can never change after the first upload)codeflutter/android/app/build.gradle.kts
targetSdk and compileSdk 36codeplayTargetSdk in app/build.gradle.kts, checked by grpc/cmd/android_release_test.go
minSdk = Flutter’s floor (API 24); the plugins need 23codeapp/build.gradle.kts
versionCode = first-parent commit count of the branch, versionName = pubspec version + commitcodeapp/build.gradle.kts; -PpulseVersionCode=<n> outside a git checkout
R8 minify and resource shrinking, not debuggable, native symbol table for Playcoderelease { … }, app/proguard-rules.pro
A release build without --obfuscate --split-debug-info is refusedcodeapp/build.gradle.kts
Permissions: internet, microphone (voice commands, assistant call), audio routing; nothing elsecodeapp/src/main/AndroidManifest.xml, checked by the test above
No cleartext traffic; no backup of app datacoderes/xml/network_security_config.xml, res/xml/data_extraction_rules.xml
Package visibility for https links, mailto: and the camera appcode<queries> in the manifest
Hi-res icon 512×512 and feature graphic 1024×500codestore/play/, drawn by grpc/tools/brandassets (-check covers them)
Phone screenshots (at least 2; 4 at 1080 px for promotion)not doneneed the app running against a deployment with real data

Build the bundle:

cd flutter
flutter build appbundle --release --obfuscate \
  --split-debug-info=$HOME/.cache/pulse-android-symbols/$(git rev-parse --short HEAD) \
  --dart-define=PULSE_BACKEND_URL=https://<the public PULSE host>

Without PULSE_BACKEND_URL the app talks to http://localhost:50051 and cannot reach PULSE from a phone; the build warns. Keep the symbols directory: flutter symbolize needs it to read a crash trace. The Build Android App Bundle workflow (manual) does the same and keeps the unsigned bundle and the symbols as private workflow artifacts; it publishes nothing.

2. Signing: owner, no secret in any repository

Play App Signing: Google holds the app signing key; the owner holds an upload key outside every repository and CI system.

  1. owner, once: create the upload key (Play needs validity past 2033-10-22):

    mkdir -p ~/.config/runink/android && chmod 700 ~/.config/runink/android
    keytool -genkeypair -v -keystore ~/.config/runink/android/pulse-upload.jks \
      -storetype PKCS12 -alias pulse-upload -keyalg RSA -keysize 4096 \
      -validity 10000 -dname "CN=PULSE upload, O=Runink"

    Keep the keystore and its password in the owner’s password manager. If it is lost, Play Console can reset the upload key; the app signing key is not affected.

  2. owner, each release, either way:

    • sign the unsigned bundle: jarsigner -keystore ~/.config/runink/android/pulse-upload.jks app-release.aab pulse-upload; or
    • build signed: copy flutter/android/key.properties.example to ~/.config/runink/android/pulse-key.properties (chmod 600), fill it in, and add -PpulseKeyProperties=$HOME/.config/runink/android/pulse-key.properties (or set PULSE_ANDROID_KEY_PROPERTIES) to the build.

    With no key given the build says UNSIGNED and produces an unsigned bundle, which Play will not accept until it is signed.

3. Play Console: owner

StepStatus
Runink organization developer account (D-U-N-S number, verified identity, fee)owner
Create the app: name PULSE, default language, App, Free, declarationsowner
App signing: accept Play App Signing (Google-generated app signing key); the first signed upload registers the upload keyowner
Google sign-in: create an Android OAuth client for org.runink.pulse with the app signing key’s SHA-1 (Test and release › App integrity)owner
Privacy policy URL: https://docs.runink.org/pulse/privacy/ (this site, website/content/privacy/). Use runink.org/pulse-privacy/ until docs.runink.org/pulse/privacy/ answers 200owner enters it
App access: sign-in is required, so give reviewers a working account and how to sign inowner
Ads: no adsowner (code has no ad SDK)
Content rating questionnaire: a business tool; no violence, sexuality, gambling or user-to-user public sharing; it does publish to the user’s own social accountsowner
Target audience: 18 and over; not designed for childrenowner
Data safety: transcribe store/data-safety.md (in the repository), answered from the codeowner
Government, financial, health apps: none applyowner
Account deletion: in-app path code (Account › Privacy and your account, IdentityService.DeleteAccount); web URL https://runink.org/account-deletion/ (names PULSE, live)code + owner enters the URL
Store listing: short and full description from store/listing.md, icon and feature graphic from store/play/, screenshotsowner (screenshots not done)
Internal testing first: create the internal track, add testers by email, upload the signed bundle, roll outowner
Closed testing, then production, when the Console allows itowner

4. Open decisions: owner

  • Payments. The Android app never sells. It is built with --dart-define=PLAY_STORE_BUILD=true (.github/workflows/build-android.yml, checked by grpc/cmd/android_release_test.go), and in that build the shared Subscription page shows the plan, seats and usage only: no list prices, plan picker, checkout, estimate or billing-portal link, and a note that the organisation’s administrator chooses the plan. Seats are bought on the web. Choose before changing that: Google Play Billing (not built) or one of Play’s external-offers programmes.
  • The public backend host. https://pulse.runink.org answers browsers. The Android app speaks native gRPC, which reaches PULSE only once TIDE’s edge passes application/grpc through over HTTP/2 (in progress); until then every call from the app fails. Build with backend_url=https://pulse.runink.org once that is live.
  • privacy@runink.org must be a monitored mailbox: the web deletion route names it.

5. Account deletion: what the code does

IdentityService.DeleteAccount (grpc/cmd/delete_account.go) checks the typed email, refuses the break-glass admin and the only admin, ends every session of the account, then deletes the account’s rows from every table that holds them (each table registers its deleter, db.RegisterAccountData) and the account itself last (grpc/internal/db/delete_account.go). The rows leave the live tables at once. Earlier versions of them, sealed under PULSE’s key, stay in the object store’s table history until the hourly compaction and the 24-hour vacuum remove them (grpc/internal/db/maintain.go). Not reached yet: sealed media in the media vault. There is no database replica: PULSE keeps no SQLite file and runs no Litestream.