q Qwetzal

Consumer wellness companion

Shipped a crash-resilient companion app that turned fragmented wellness UX into one measurable retention loop.

Consumer wellness companion

“Retention stopped being a mystery once everyone meant the same thing when they read the funnel — finally.”

Head of Product, Confidential consumer health
Cross-functional coordination supporting wellness product velocity

Programme imagery anchoring the client narrative — continuity between qualitative testimony and shipped surfaces.

01

THE PARTNERSHIP BEGINS

The programme began where trust breaks first: habits people repeat under imperfect networks.

A Flutter cross-platform product with offline-first habits, biometric access, and health-data integrations — backed by a Laravel API and event-driven analytics. The programme unified fragmented mobile surfaces into a cross-platform client with trustworthy health-data handling and telemetry product teams could operate.

02

THE PARTNERSHIP EXPANDS

Multiple experiments diverged — retention signals stayed opaque while integrations multiplied QA risk.

What they needed

Confidential — consumer health — a product team with strong wellness content but fragmented mobile experiences. Engaged Qwetzal to ship one cross-platform companion with trustworthy data handling and analytics they could act on.

What stood in the way

Retention hinged on frictionless daily rituals across flaky connectivity — native integrations needed parity without exploding QA surfaces. Legacy experiments couldn’t reconcile offline queues with analytics-grade instrumentation.

  • Multiple prototype builds diverged on UX and event schemas.
  • Biometric gates and partner integrations duplicated fragile native bridges.
  • Analytics pipelines rarely survived release cadence — retention loops were opaque.
03

STRUCTURING THE PLATFORM

One companion experience with consent-aware data handling and telemetry teams could finally act on.

How we intervened

  • — Designed daily rituals to survive real-world connectivity — not demo-grade Wi‑Fi.
  • — Aligned product, growth, and clinical stakeholders on what “truth” meant in analytics before velocity resumed.
  • — Protected sensitive access paths without turning authentication into a retention cliff.
  • — Treated stability and retention metrics as release gates — not post-mortem surprises.
04

THE PLATFORM REACHES PRODUCTION

Stores and staged rollout followed hardening work — hypercare watched stability like a product metric.

Release trains stayed bounded by crash budgets; device labs covered biometric and integration paths before reviewers saw builds. Growth shipped knowing events meant the same thing on both platforms.

05

TRANSFORMATION AT SCALE

Impact showed up where budgets, operators, and auditors actually look — not only in sprint notes.

Crash-free sessions sustained above 99.7% while activation lifted materially after onboarding refinements shipped mid-programme.

120k

Installs after the launch window

4.8★

App store rating across regions

99.7%

Crash-free sessions in production

+31%

Activation lift after onboarding redesign

OPERATING REALITY — BEFORE AND AFTER

Retention stopped being an opinion once instrumentation meant the same thing in London and Lagos.

Release confidence

Stores and regulators punished instability — every train had to earn trust.

Before

Ad-hoc QA matrices — regressions surfaced days after reviewers blessed builds.

After

Crash-budgeted release trains with hardware labs gating promotion until budgets stayed green.

Data lineage

Growth couldn’t debate funnel definitions while experiments diverged.

Before

Fragmented event naming across prototypes — analysts reconciled schemas manually.

After

Versioned analytics contracts — warehouses and growth teams finally shared identical causal definitions.

Retention signals

Activation lifts needed causal telemetry — not vanity dashboards.

Before

Opaque drop-offs — teams argued hypotheses without shared instrumentation.

After

Funnel telemetry tied to product bets — leaders rehearsed decisions against consistent reads.

Partner integrations

Health partners demanded deterministic replay — not tribal QA folklore.

Before

Brittle one-offs duplicated native bridges with uneven parity.

After

Adapter layer with replay fixtures — regressions diagnosed before users felt them.

THE CONNECTED ECOSYSTEM

Extended outcomes across operators, finance, and partner workflows once the programme became authoritative.

  • Scaled installs past 120k within the launch window without breaching crash budgets.
  • Unified retention telemetry across iOS and Android for the first time.
  • Reduced time-to-diagnose integration regressions from days to hours.
06

THE CONNECTED OPERATING MODEL

Capabilities packaged so teams inherit how the organisation runs — not a maze of bespoke fixes.

Offline-first habits

Offline-first habits

Daily rituals that stay coherent when connectivity drops — users keep momentum instead of abandoning the loop.

Sensitive access

Sensitive access

Unlock flows that respect device norms without turning security into friction that kills activation.

Partner health data

Partner health data

Ingestion paths normalised under consent — fewer surprises for privacy reviewers and users alike.

Growth signals

Growth signals

Telemetry aligned to retention hypotheses so bets became measurable instead of ideological.

Operator levers

Operator levers

Tooling for cohorts and safe experimentation without shipping chaos to app stores.

Respectful outreach

Respectful outreach

Notifications bounded by preference centres and regional expectations — fewer uninstall spikes.

What they received

  • ✓ Production-ready builds for iOS and Android
  • ✓ Backend services sized for growth
  • ✓ Privacy / DPIA documentation package
  • ✓ Staged rollout posture with rollback rehearsal
  • ✓ Runbooks for integrations and incidents
  • ✓ Thirty-day launch hypercare
07

INTELLIGENCE

Questions leadership asks before committing capital and calendar.

How did you validate biometric flows? +

Hardware labs across mid-tier devices plus scripted replay suites for edge cases before store submission.

Can integrations expand without app resubmission? +

Server-driven configuration ships toggles where policy allows; deeper native changes still ride the release train with regression gates.

Who operates analytics post-handover? +

Client growth teams — we transferred schema docs, debugging guides, and dashboards wired to their warehouse.

How were privacy reviews handled? +

Data minimisation baked into adapters; DPIA artefacts updated each sprint with legal stakeholders.

Related programmes

All work
Diginature

SAAS

Diginature

Nature and outdoor programmes supported by modern digital workflows
Doril Labs

SAAS

Doril Labs

A unified diagnostic network from lab core to patient devices.
Hello Institute

TRANSFORMATION

Hello Institute

Optimizing educational throughput and student lifecycle

Next engagement

Have a similar challenge?

Tell us about your product and timelines — we'll respond within one business day with relevant references.

Send a brief