Every nutrient, every vital, one dashboard
Açaí reads and writes HealthKit bidirectionally. That means the 245 micronutrients per meal you log end up in Apple Health, next to your HRV, sleep, and activity. Whatever reads from HealthKit (Oura, Whoop, Levels, Eight Sleep, a future version of Siri that actually knows what you ate) now has nutrition as a correlated input.
Açaí writes to Apple Health
- MacrosCalories, protein, carbohydrate, fat, fiber, sugar, saturated fat, monounsaturated fat, polyunsaturated fat
- VitaminsA, B1, B2, B3, B5, B6, B7, B9 (folate), B12, C, D, E, K
- MineralsCalcium, iron, magnesium, phosphorus, potassium, sodium, zinc, copper, manganese, selenium, iodine, chromium, molybdenum
- WaterWater intake in ounces or milliliters
- CaffeineEstimated caffeine content per logged meal or drink
Açaí reads from Apple Health
- ActivityActive calories, steps, exercise minutes, flights climbed
- BodyWeight, lean body mass, body fat percentage
- SleepTotal time in bed, REM + deep + light phases
- VitalsResting heart rate, heart rate variability, respiratory rate
One-way sync is a partial tracker
Some nutrition apps only write to Apple Health. That’s useful, but it means your BMR calculation inside the app is still guessing at your activity level. Açaí reads active calories directly from HealthKit, so the deficit tracker updates in real time as you move, without manual activity entry.
The other side matters too. Because we write all 245 micronutrients into HealthKit, any other app that subscribes to HealthKit nutrition data automatically inherits Açaí’s depth. Oura’s next insights engine, Whoop’s recovery model, Levels’ glucose correlation, all of it reads from the same underlying HealthKit store.
We chose bidirectional because iOS is a garden of services reading from one shared data layer. If Açaí only wrote, it would be a silo. Reading and writing means our data is in the same pool as everyone else’s.
Make Apple Health actually useful.
Açaí fills the nutrition gap in HealthKit with 245 fields per meal.