> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://blueprint.ziro.health/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://blueprint.ziro.health/_mcp/server.

# Multi-Platform Strategy

Health applications increasingly span multiple platforms. A patient might check their data on a phone, review trends on a web dashboard, receive reminders through a smart speaker, and collect data from a wearable.

## Platform Selection for Health Apps

| Platform         | Best For                             | Considerations                                    |
| ---------------- | ------------------------------------ | ------------------------------------------------- |
| iOS (Native)     | Patient apps, health kit integration | Swift, Apple Health, strict App Store review      |
| Android (Native) | Broader reach, Health Connect        | Kotlin, device fragmentation                      |
| React Native     | Cross-platform efficiency            | Shared codebase, native health SDK limitations    |
| Web (PWA)        | Clinician dashboards, admin portals  | Accessibility, responsive design, offline support |
| Wearable OS      | Passive monitoring                   | watchOS, Wear OS, limited UI                      |
| Voice            | Hands-free interactions              | Alexa, Google Assistant, HIPAA compliance         |

## Apple Health and Google Fit Integration

Health platform integration is table stakes:

* **Apple HealthKit**: Read/write steps, heart rate, sleep, workouts, nutrition, glucose, blood pressure
* **Google Health Connect**: Modern Android health data platform
* **Apple ResearchKit**: Framework for health research applications
* **Apple CareKit**: Framework for care management apps

## Voice Interface Patterns

Voice is emerging as a health interaction modality:

* **Medication reminders**: "Time to take your blood pressure medication"
* **Symptom logging**: "Tell me how you're feeling today"
* **Appointment scheduling**: "Book my next follow-up"
* **Data queries**: "What was my blood sugar this morning?"

## Cross-Platform Sync and Offline

Health apps must work reliably across connectivity states:

* **Local-first architecture**: Store data locally, sync when connected
* **Conflict resolution**: Deterministic merge strategy for concurrent edits
* **Offline encryption**: Data encrypted on device using platform Keychain/Keystore
* **Selective sync**: Prioritize critical data (alerts) over less urgent data