Show the source
A health trend without provenance is easy to overread. Akros keeps the source, freshness, and comparison window close to the conclusion.
Why Akros exists
Health data is abundant. Context is still scarce.
Apple Health can hold years of measurements. A lab portal can hold important snapshots. Neither automatically tells you what changed, what baseline matters, or whether a conclusion is supported by enough data.
The product decision
Akros is built as a source-aware health record, not an all-purpose coach. It reads only the Apple Health categories a person approves, accepts a deliberately selected PDF, and creates bounded comparisons from defined time windows.
The weekly briefing compares the current seven days with the preceding 28 days. When there is not enough data, the right output is not a motivational paragraph. It is a clear statement that no conclusion should be drawn yet.
This narrower product is more useful because every visible promise can be tested. A user can see the source, check the original report, understand the limit, and take the record elsewhere.
Four operating principles
Say when the data is thin
Missing days, short history, and uncertain PDF extraction are product states, not errors to hide with confident language.
Keep the promise narrow
Akros organizes personal wellness data. It does not diagnose, prescribe, infer causes, or replace the relationship between a person and a clinician.
Make leaving possible
A useful record should not become a lock-in mechanism. Export and account deletion are part of the core product contract.
Business model
Subscriptions, not attention.
Akros is funded by optional Pro subscriptions. There are no ads and no sale of health data. The free tier exists to prove the workflow before asking for payment.
Built in Australia
Small product. Explicit responsibility.
Akros is built in Sydney. Product questions, privacy requests, and bug reports have one support path so issues cannot disappear between vendors.
See the contract