Skip to content

Android v1.5.1 — futuristic hero front screen + share-for-growth

Choose a tag to compare

@vasilyespana vasilyespana released this 17 Oct 21:29

CallPages for Android v1.5.1 — futuristic hero front screen + share-for-growth

Downloads (served from callpages.me):

This GitHub release carries notes only — the binaries live in this repo's downloads/ (commit ae4cbe12519ca2f7710f71277993d13a470bc881) and are streamed by the CallPages worker at the callpages.me URLs above, pinned by commit + sha256. (GitHub asset upload is blocked by a credential limit, uploads.github.com 401 — same as v1.4.3/v1.4.4/v1.5.0.)

What is new

  • Futuristic hero front screen (PR #334): the signed-out landing is now a full-bleed hero — generated holographic voice-wave artwork over a glowing phone, a slow cinematic zoom, the CallPages wordmark and ONE line: "Your business phone that answers itself." (Spanish on Spanish devices.) No more feature-paragraph wall. Signed-in owners still skip it entirely — the own-session launch restore is untouched.
  • Share for growth (PR #334): a Share button on the front screen shares the app itself ("Get CallPages — your business phone that answers itself: https://callpages.me/android"), and every page's detail screen gains Share my page, sending the owner their public link — Call <Business> on CallPages: https://callpages.me/p/ — through the standard Android share sheet.

Verification

  • JVM unit suite: 155/155 passed on the merged staging tree (147 v1.5.0 baseline + 8 new ShareKit tests).
  • apksigner: both APKs verify, APK Signature Scheme v2, signer cert SHA-256 afff8f4bbb86874d9682d90a4e795211e6d8ee397d8dc612561ea3638dd2b396 (same release certificate — in-place update over v1.5.0).
  • aapt2: package me.callpages.merchant, versionName 1.5.1, versionCodes arm64 112 / armeabi-v7a 111, launchable MainActivity, per-ABI native code.
  • Cloud-device leg not run (BrowserStack minutes exhausted) — composite evidence per the v1.4.3/v1.4.4/v1.5.0 precedent.

Known gap (not in this release)

Consumer (customer) sign-in is NOT in v1.5.1: the customer backend has no native token-exchange endpoint the app can call (the customer session is issued only by the web browser OAuth flow as an HttpOnly cookie). The app-side build is ready to proceed the moment the worker gains POST /api/v1/auth/customer/google.