Android v1.6.0: the full-parity release

CallPages Android v1.6.0 is the full-parity release: completely native — no web views anywhere — with every web dashboard surface built in, from Activity and Appointments to Support, Sales and API keys. Every editor autosaves the moment a change is confirmed, and the app updates itself. The APKs on the download page were verified byte-for-byte against the signed builds.

An owner runs their business from their phone, but the app lagged the web dashboard badly: when parity was measured honestly, only 11 of 41 capability rows were fully native — the rest were partial, missing, or broken, and some ‘features’ were web pages wearing an app costume. A phone app that makes you go back to the browser for half your work is not an app. v1.6.0 closes the gap in one release.

Parity is a number, and now it’s a good one

The parity matrix is the contract: every capability the web dashboard has, listed as a row, marked FULL, PARTIAL, MISSING or BROKEN from evidence — tests and drives, not intentions. v1.5.2 measured 27% fully native. v1.6.0 measures 43 of 47 rows FULL, with zero missing and zero broken. The four PARTIAL rows are printed in the app team’s release packet with their blockers named; each is a server endpoint away, and each will move to FULL when its endpoint lands — in a release note like this one, not in a footnote nobody reads.

Autosave, as a platform rule

The web Store editor and Website Studio shipped autosave this week; the app holds the same line. In v1.6.0 there is no screen where work can be lost to a forgotten Save button, because there are no Save buttons: confirm a change and it is already being written, with the same honesty rules — a failed write says so instead of pretending.

The release process is part of the feature

Both processor variants (arm64 and armeabi-v7a) are signed with the same release key as v1.5.2, so the app updates in place — and from this version on, it can fetch those updates itself, verifying the SHA-256 before installing. The builds on the public download page were downloaded back and compared byte-for-byte with the signed artifacts. One honest limit, repeated from the summary because it matters: no cloud-device run backs this release (the lab was exhausted); the evidence is the 402-test JVM suite, the signer/ABI static gate, and the byte verification. When device proof resumes, it will be reported the same way.

How it works

1. Completely native: Activity, Pages, native Analytics, Appointments, Calendar, Support, Sales, API keys, Billing routing, exports, Owner Bridge and the Learning Center are built into the app. No web views anywhere.
2. Autosave everywhere: every editor — products, collections, pages, settings — persists the moment a change is made or confirmed. A Save button appears nowhere in the app; that is a rule of the platform now, not a preference.
3. The catalog is the unified Store editor from the web release: products edited inside collections, with the same product and collection hide and product delete, over the same data.
4. Self-update ships in this release: the app checks the version manifest, and one tap downloads the new build, verifies its SHA-256, and installs it — same signing key, in place.
5. Measured, not vibes: parity went from 11 FULL / 10 PARTIAL / 17 MISSING / 3 BROKEN (41 rows) to 43 FULL / 4 PARTIAL / 0 MISSING / 0 BROKEN across the expanded 47-row matrix.
6. What is NOT claimed, said plainly: the four PARTIAL rows are blocked on named server-side pieces (a billing status read, an agent-settings write that doesn’t persist yet, push device registration, and end-to-end sign-in device proof), and this release carries no cloud-device test run — the device lab budget was exhausted. Verification for v1.6.0 is the full JVM suite (402/402), the static signer and ABI gate, and byte-identical production downloads — strong checks, and not a substitute we dress up as device proof.

See it live: Mi Junta

Mi Junta — CallPage · Mi Junta — website

The download surface, captured from production: v1.6.0 with its SHA-256 checksums published next to the button. The served APKs were downloaded back and matched byte-for-byte to the signed release builds — what the page offers is what was tested.

Related reading

• Callbacks and appointments moved in: Activity holds everything now
• Así lanzamos los dominios personalizados: tu página de CallPages, en tu propio dominio
• Delete that actually deletes — and a Hide that keeps selling
• Release notes 2026.10.20

Get the Android app →

---

Innovation by Vasily Starostenko, founder of CallPages.