Native apps

Two apps, one codebase, shipped in phases

SilverGuard Family goes first because it carries the least risk. SilverGuard Senior ships as a thin consent and SOS app. The SGOS device agent waits until the named security owner and tested failsafe exist.

Pilot, now to Q1 2027Phase 2, post Q1 2027
Interactive preview

Tap through the pilot screens

These are wireframe previews rendered in the browser, not store builds. They set the interaction bar for the Flutter implementation.

SilverGuard Family

9:41Family100%
Margaret R.
Protection active, 0 blocked this week

Caregiver facing. Alerts, case status, Trusted Circle, one tap to a human advocate.

SilverGuard Senior

9:41Senior100%

Good morning, Margaret.

You are protected.

We are watching for scam calls and texts. You do not need to do anything.

One tap reaches a real person. No device lock, no automatic actions.

Large type, plain language, phone support fallback. No background monitoring in the pilot.

Scope

What ships when

Pilot, now to Q1 2027

Family app, now to Q1 2027

  • Auth and onboarding

    Invite code entry tied to the web closed beta, then biometric unlock.

  • Alert inbox

    Native push with reason codes and next steps, tap through to case detail.

  • Trusted Circle

    Up to five members, per member notification preferences.

  • Case status

    Read only advocate review state, same source as the web app.

  • Quick contact

    One tap to the assigned advocate or to the senior.

Phase 2, post Q1 2027

SGOS agent, gated

  • Android SGOS agent

    Device Admin enrollment, remote lock, remote access app kill list.

  • iOS SGOS agent

    MDM profile or Guided Access fallback, App Review risk validated first.

  • BLE pendant

    Core Bluetooth pairing and background presence.

  • Signed rules

    Client refuses unsigned rule distribution, no exceptions.

Gate, not a date. Phase 2 starts when the named security owner and tested life safety failsafe exist, because a compromised signing key must never lock every enrolled device.

Stack

Flutter, Firebase, one client stack

  • Framework, Flutter. Same choice as the SGOS desktop agent, so there is one client stack to maintain.
  • Build, Replit. Android builds run in Linux containers. iOS signing still needs a macOS step, Codemagic or Xcode, confirm before scoping.
  • Backend, Firebase and Vertex AI. Auth, Firestore, Cloud Messaging, Cloud Functions, Gemini. No parallel backend for mobile.

Store submission notes

Phase 1 review

Android: Standard consumer review, no Device Admin requested

iOS: Standard consumer review

Phase 2 review

Android: Additional Play policy review for Device Admin, confirm current policy

iOS: High scrutiny, likely enterprise distribution track

Privacy disclosure

Android: Data safety form matches real telemetry

iOS: App Privacy label matches real SDK behavior

Beta channel

Android: Play internal or closed testing, cohort matched

iOS: TestFlight, same cohort mapping

Open dependencies

Security owner

Named owner and tested failsafe, the same blocker as the Draper pilot.

Apple path

MDM or enterprise distribution validated before Phase 2 iOS is scoped.

iOS signing

Confirm whether Replit covers signing end to end or needs a bridge service.