# CarePulse Connect — Google Play release pack (v5.0.0, versionCode 5)

## 1. Build the release bundle
1. Android Studio (Ladybug or later) → open `android/CarePulseConnect`. Accept the Gradle / AGP upgrade prompt if offered.
2. Create the **upload key** once and keep it safe (Play App Signing holds the app signing key):
   `keytool -genkeypair -v -keystore carepulse-upload.jks -alias carepulse -keyalg RSA -keysize 4096 -validity 10000`
3. Create `android/CarePulseConnect/keystore.properties` (ignored by git):
   ```
   storeFile=/secure/path/carepulse-upload.jks
   storePassword=…
   keyAlias=carepulse
   keyPassword=…
   ```
4. `./gradlew :app:bundleRelease` → `app/build/outputs/bundle/release/app-release.aab`.
5. Test the release build on Android 8, 12, 14 and 16 phones: pairing (code + QR), BP monitor + oximeter over Bluetooth,
   Health Connect permission screen, offline queue (airplane mode → readings send later), My medicines (Taken / puffs).

Targets **API 36 (Android 16)** — Google Play has required this for new apps and updates since 31 Aug 2026. The app draws
edge-to-edge (Android 16 enforces it); every screen is padded for the system bars. No native libraries, so the 16 KB page-size rule is met.

## 2. Store listing (English – India)
| Field | Text |
|---|---|
| App name (≤30) | CarePulse Connect |
| Short description (≤80) | Send BP, SpO₂, sugar & weight readings to your hospital care team. |
| Category | Medical |
| Tags | Health monitoring, Medical devices |
| Contact e-mail | support@caresoft.co.in (confirm) |
| Website | https://iot.caresoft.co.in |
| Privacy policy | https://iot.caresoft.co.in/app-privacy-policy/ |

**Full description**

CarePulse Connect links your home health devices to the hospital that is looking after you.

Your hospital gives you a pairing code or QR code. After pairing, readings from your Bluetooth BP monitor, pulse oximeter, glucometer,
thermometer and weighing scale reach your care team automatically — no typing, no photos on WhatsApp.

• Take a reading: the app finds your device and sends the result to the hospital.
• Always listen: readings are picked up in the background when you measure.
• No Bluetooth device? Type the reading, or take a photo of the device screen.
• Share data from your watch through Health Connect – only the types you choose.
• My medicines: see today's doses and tick them off; log rescue-inhaler puffs.
• Works offline: readings wait on the phone and send when you are back online.

Your readings go only to your hospital. Your care team sets your targets and is alerted when a reading needs attention.

CarePulse Connect is used with a hospital or clinic programme (CarePulse IoT by Caresoft). It does not diagnose, and it is not for
emergencies — if you feel unwell, call your doctor or emergency services.

**Graphics:** icon 512×512 (from `res/drawable/ic_launcher`), feature graphic 1024×500, at least 4 phone screenshots
(Home, Take reading result, My medicines, Health Connect sharing). Use the DEMO hospital — no real patient data.

## 3. App content declarations (Play Console → Policy → App content)
| Item | Answer |
|---|---|
| Privacy policy | URL above |
| Ads | No ads |
| App access | Restricted: needs a hospital pairing code. Give reviewers a **demo pairing code** (create a phone gateway for the DEMO hospital and paste its code + "server: https://app.carepulse.caresoft.co.in") and say it expires in 30 days. |
| Content rating | IARC questionnaire → Medical / reference, no user-generated content shared publicly → expected "Everyone / 3+" |
| Target audience | 18 and over (patients use it with their caregivers) |
| News app | No |
| Health apps declaration | Medical: "Remote patient monitoring – sends readings from connected devices to the user's healthcare provider". Not a medical device in itself (the hospital's CarePulse platform does the alerting) – keep this consistent with the CDSCO opinion. |
| Health Connect | Declare each read permission with its purpose: blood pressure, heart rate, resting heart rate, HRV, SpO₂, glucose, weight, body temperature, respiratory rate, steps, active calories, sleep, background read → "shared with the user's care team for remote monitoring". Read only, no writes. |
| Foreground service | `connectedDevice` type — "listens for the patient's Bluetooth medical devices while monitoring is switched on" (short video of the toggle may be requested). |
| Financial features / government | No |

## 4. Data safety form
| Data type | Collected | Shared | Purpose | Optional? |
|---|---|---|---|---|
| Health info (readings, medicines taken) | Yes | No (sent to the user's own hospital, which is the controller) | App functionality | Required |
| Fitness info (steps, activity, sleep via Health Connect) | Yes | No | App functionality | Optional |
| Personal info: name, phone (shown from hospital record) | Yes | No | App functionality, account management | Required |
| Device or other IDs (device model, Bluetooth device serial) | Yes | No | App functionality | Required |
| Photos (photo of device screen) | Yes | No | App functionality | Optional |
| Location | No (Bluetooth scan uses `neverForLocation`) | | | |

Data is encrypted in transit (HTTPS only, cleartext disabled). Users can ask their hospital to delete data; unpairing removes it from the phone.

## 5. Release
Internal testing (Caresoft team) → Closed testing (pilot hospital staff + 10–20 patients, 14 days; new personal developer
accounts need 12+ testers for 14 days before production — Caresoft's organisation account is exempt) → Production, staged rollout 20 % → 100 %.
