Bug: Apple Health data is unstructured (should be stored as a HKCorrelation)
Cronometer incorrectly records data in Apple HealthKit.I use several different apps that analyze food and activity data tog
Each logged food gets stored as an individual nutritional data record instead of being stored as a food. This means other apps that read the data have no idea what you ate or drank. All they see is a bunch of disconnected nutritional data points and the time they were recorded. In practice, it means food won’t show up in all apps (as they don’t expect data to be unstructured) and you miss out on correlations and insights from Apple Health, Guava, and other apps that analyze the data.
One food item (one logged item in Cronometer) should be stored as a HKCorrelation of type food that contains all the nutrient records. This HKCorrelation should also contain a HKMetadataKeyFoodType, which is a string representing the food (e.g., "Honey" or "Apple").
Fixing this would make Cronometer’s nutritional integration with Apple Health would be on-pair with the structured data that your app already provides to Android Health Connect users.