EHG SmartWellness Enhance your Health Goals
Mobile Application Proposal

The EHG Smart Band, reimagined as a native wellness experience.

A phased proposal to design and build the EHG SmartWellness mobile application — a Flutter-based iOS and Android app that connects directly to the EHG Smart Band, replacing the manufacturer's white-label application with a fully branded, privacy-first wellness experience.

EHG Smart Band
EHG Smart Band
EHG Smart Band
Phase 01 — Foundation
140hours approx. · V1
Fully local, offline wellness application with direct band connectivity.
£5,000 estimated
Phase 02 — Connected Wellness
170hours approx. · V2
Backend, admin panel, membership and account-based entitlements.
£6,000 estimated

Client Snapshot

Client
EHG SmartWellness Ltd
Website
ehgsmartwellness.com
Sector
Connected wellness — smart wearables & activewear
Product in Scope
EHG Smart Band — BLE wellness wearable
Prepared by
Kretoss Technology Custom Software & Mobile
kretoss.com
DocumentV1 & V2 Scope + Estimate
Executive Summary

A phased path from a private, on-device wellness app to a connected membership experience.

This proposal outlines the design and development of the EHG SmartWellness mobile application in two clearly separated phases. Both phases are scoped directly from the approved HTML prototype and the manufacturer's iOS and Android SDK documentation, so there is no ambiguity about what is being built.

V1Local & Offline Foundation

A complete, production-ready wellness application that pairs with the EHG Smart Band and keeps all health data — vitals, sleep, and journal entries — permanently on the user's device. No account, backend, or cloud dependency of any kind.

V2Connected Wellness Layer

An optional account, membership, and rewards layer — with a web-based admin panel, Apple and Google in-app purchases, and a wardrobe/programme system — built strictly on top of V1 without ever moving health data to the cloud.

Scope discipline: every feature in this proposal is drawn directly from the supplied HTML prototype and manufacturer SDK documentation. No additional functionality has been assumed or introduced beyond what is described in this document.
Project Understanding

Replacing the manufacturer's white-label app with an EHG-native experience.

EHG SmartWellness is building its own iOS and Android application to fully replace the manufacturer's generic wearable app. The new application will connect directly to the EHG Smart Band over Bluetooth Low Energy, using the manufacturer's proprietary native SDKs, and present the resulting data through a bespoke wellness experience already validated in your HTML prototype.

Hardware

The EHG Smart Band communicates via Bluetooth Low Energy using the manufacturer's proprietary protocol. Documentation referring to a "Ring" is understood by both parties to apply equally to the EHG Smart Band.

Design

No UI/UX design work from scratch is required. The provided HTML prototype is the primary source of truth for screens, flows, and interaction patterns across the application.

Integration

Native iOS and Android SDKs are bridged into the Flutter application using Flutter Platform Channels, giving the app native-grade access to the band while keeping one shared codebase.

Proposed Architecture

From wearable signal to wellness insight.

A single, consistent data path carries information from the EHG Smart Band to the screen — native where it must be, shared where it can be.

EHG Smart BandBluetooth Low Energy hardware
↓
Bluetooth Low EnergyWireless transport layer
↓
Manufacturer Native SDKiOS (Objective‑C) · Android (.aar)
↓
Native iOS / Android LayerPlatform-specific SDK bridging
↓
Flutter Platform ChannelsNative ↔ Flutter communication bridge
↓
Flutter ApplicationShared iOS / Android codebase
↓
Wellness ExperienceDashboard · Vitals · Training · Journal
V1 · BLE Architecture

Device connectivity, built for real-world conditions.

Reliable pairing, reconnection and historical sync are the backbone of V1 — the app must behave predictably even when Bluetooth conditions are imperfect.

Connection Lifecycle

  • Permission handling on iOS & Android
  • Device discovery & scanning
  • Pairing, connection & disconnection
  • Automatic reconnection handling
  • Battery, firmware & device information
  • Forget / unpair device

Historical Synchronization

  • Retrieval of supported historical wearable data
  • Duplicate-record prevention on sync
  • Local persistence of all synced records
  • Graceful handling of reconnect / re-sync scenarios
  • Historical wellness information display
Version 1 Delivery Plan

V1 Milestones

Delivered across four sequential milestones, each ending in a working, testable build.

01

Flutter Foundation & Native SDK Setup

  • Flutter architecture
  • iOS & Android SDK setup
  • Platform Channels
  • BLE permissions & initial discovery/connection
02

BLE Device & Health Data Integration

  • Device pairing, connection & reconnection
  • Device information & battery
  • Health data synchronization
  • Historical data & local data models
03

Wellness Application Experience

  • Dashboard & Vitals
  • Readiness & wellness score
  • Move / Recover / Mind / Fuel
  • Training, journal & recommendations
04

Settings, Data Export & QA

  • Settings & data/privacy controls
  • Export / delete & device management
  • Offline & BLE testing
  • iOS/Android QA, bug fixing & release readiness
Total V1 Effort
140development hoursapprox.
Estimated V1 Investment
£5,000

Hours are an approximate estimate for the V1 scope defined above, quoted at an estimated £5,000. Final hours may vary within a reasonable margin depending on manufacturer SDK behaviour and hardware testing outcomes.

V2 · Backend & Admin Architecture

An account layer that never touches health data.

Flutter Application (V1 Foundation)Local wellness experience, unchanged
↓
Secure Account APIAuthentication & account sync
↓
Backend & DatabasePoints · membership · wardrobe · programmes
↓
Web Admin PanelAccount & membership management only
Version 2 Delivery Plan

V2 Milestones

Delivered across five milestones, building outward from the account foundation to a fully tested connected experience.

01

Backend & Account Foundation

  • Backend architecture & database
  • Authentication & user accounts
  • Secure account synchronization
02

Admin Panel

  • Admin authentication & dashboard
  • User & membership management
  • Points, rewards, wardrobe & programmes
03

Membership & Store Entitlements

  • Apple IAP & Google Play Billing
  • Purchase validation & restore
  • Signed redemption codes
04

Wardrobe, Programmes & Integration

  • Wardrobe & programme sync
  • Points & rewards
  • Mobile / admin integration
05

QA, Security & Production Readiness

  • API & admin testing
  • Membership & cross-platform testing
  • Security checks & bug fixing
Total V2 Effort
170development hoursapprox.
Estimated V2 Investment
£6,000

Hours are an approximate estimate for the V2 scope defined above, quoted at an estimated £6,000. V2 is quoted and commissioned separately from V1.

Optional Scope Item

Live Shopify Admin API order lookup and validation

The base V2 scope uses signed unlock codes delivered through order messaging — no live e-commerce dependency is required. A live Shopify lookup is available as a separate, optional item outside the 170-hour V2 estimate.

Included in V2

Signed Unlock-Code Workflow

Codes are generated per order and delivered via the Shopify/Amazon order message. The app validates the code locally — no live storefront connection required.

Optional / Separate Estimate

Live Shopify Admin API Lookup

Direct, real-time order lookup and validation against the Shopify Admin API. Offered for comparison as an additional scope item, estimated separately if selected.

Shopify-certified team: our team includes a Shopify-certified developer, so either route — and any related storefront, Admin API or theme work on ehgsmartwellness.com — can be supported directly by us rather than a separate agency.
Technology Stack

A shared codebase, native where it matters.

Backend technology remains flexible for final confirmation with your team; the mobile and integration stack is fixed by the manufacturer SDKs.

LayerV1 — FoundationV2 — Connected Wellness
ApplicationFlutter, DartSame Flutter application, extended
Native iOSObjective‑C manufacturer SDK—
Native AndroidAndroid .aar manufacturer SDK—
BridgingFlutter Platform Channels—
ConnectivityBluetooth Low Energy—
StorageLocal database / on-device storageBackend database PostgreSQL
Backend—Node.js
Admin—Web-based admin panel in React.js
Commerce—Apple IAP · Google Play Billing · Shopify where applicable
Auth—Secure account authentication
Privacy & Data Architecture

Health data stays on the device. Always.

This principle holds across both phases of the project — it is not a V1-only limitation that V2 relaxes.

🔒Stays Local — Never Synced

  • Vitals & all wearable health metrics
  • Sleep data
  • Journal entries & notes
  • Wearable history

☁️May Sync via Optional Account (V2)

  • Wellness points
  • Membership status
  • Redemption codes
  • Wardrobe & programme progress
Admin panel restriction: the V2 admin panel manages accounts, membership and commerce data only. It never exposes or stores user health, vitals, sleep or journal data.
Testing & Quality

Validated on real hardware, not just simulators.

BLE behavior depends on the physical device, firmware version, and manufacturer SDK version — final validation against real EHG Smart Band hardware is required before release.

iOS testing
Android testing
Real wearable device testing
BLE connection testing
Pairing / reconnection testing
Historical sync testing
Offline testing
Local persistence testing
Data export/delete testing
Membership testing (V2)
IAP testing
Google Play Billing testing
Backend / API testing
Admin panel testing
Regression testing
Important Assumptions

What this proposal depends on.

Out of Scope / Change Requests

Anything outside the agreed scope is a change request.

Functionality not listed in the agreed V1/V2 scope above will be treated as a change request and estimated separately, on request.

New wearable device models
New SDK functionality
Additional health metrics
New third-party integrations
New payment providers
Additional e-commerce integrations
Major UI/UX redesign
Additional languages
New backend features
New admin reports
Deliverables

What is delivered at the end of each phase.

V1 Deliverables
  • Flutter iOS application
  • Flutter Android application
  • Native iOS & Android SDK integration
  • BLE wearable connection
  • Local health/wellness storage
  • Complete V1 prototype functionality
  • Data export / delete
  • Tested, production-ready build
V2 Deliverables
  • V1 enhancements required for V2
  • Backend / API & database
  • Admin panel & account system
  • Membership, Apple IAP & Google Play Billing
  • Points, rewards & redemption codes
  • Wardrobe & programme progress
  • V2 production-ready integration
Support & Added Value

What you get beyond the delivered build.

Two commitments are included with this engagement at no additional cost: certified Shopify support for anything the app needs from your storefront, and two months of free maintenance after each phase goes live.

Included · No extra cost

Shopify Certified Developer

EHG runs on Shopify, and our team includes a Shopify-certified developer. Any storefront-side work the app depends on — order messaging for unlock codes, product and metafield setup, Admin API credentials, or theme and checkout adjustments — can be handled by the same team building the app. You will not need a second vendor to bridge the store and the application.

2 months · Free

Free Maintenance Support

Each phase ships with two months of free maintenance from its go-live date. If a defect is found in delivered functionality within that window, we fix it at no charge — including crashes, BLE or sync faults, and regressions that appear after routine iOS, Android or SDK updates.

Discussed separately

New Features & Enhancements

Maintenance covers defects in what has already been delivered, not new functionality. Any new feature, additional health metric, further integration or design change requested after delivery is scoped, quoted and agreed separately — so the free support window stays genuinely free and the scope stays unambiguous for both sides.

2Months Free

Bug-fix and maintenance support is included with both V1 and V2, starting the day each phase goes live — at no additional cost, and on top of the estimates quoted in this proposal.

What maintenance covers: defects and unexpected behaviour in functionality already delivered and signed off under the agreed V1/V2 scope. It does not cover new features, third-party service costs, manufacturer SDK changes that alter the agreed behaviour, or content and account administration — these are handled as separate, individually estimated items.
IP, Source Code & Ownership

Ownership & Delivery

  • Custom application source code developed specifically for EHG SmartWellness Ltd will be assigned to EHG SmartWellness Ltd according to the agreed contract and payment terms.
  • Source code will be committed and provided at each completed milestone.
  • The Git repository will be held under EHG SmartWellness Ltd ownership.
  • The Apple Developer account will be owned by EHG SmartWellness Ltd.
  • The Google Play Console account will be owned by EHG SmartWellness Ltd.
  • Backend and cloud accounts will be owned by EHG SmartWellness Ltd.
  • Third-party manufacturer SDKs remain subject to the manufacturer's own licensing terms.
  • Our team will not claim ownership of any third-party SDK or third-party library.
Final Next Steps

Ready to move from prototype to product.

Once the scope in this document is confirmed, here is how the engagement begins.

01

Confirm Scope

Review and confirm the V1 and V2 scope defined in this proposal.

02

Share Access

Provide manufacturer SDKs, hardware, and developer account access.

03

Kick Off V1

Begin Milestone 1 — Flutter Foundation & Native SDK Setup.

04

Review & Iterate

Milestone-by-milestone review, with source code delivered at each stage.