Beta FAQ & Known Limitations

What does “beta” mean?

Omnio is feature-complete but still in active development. During the beta period:

Core features work — Device syncing, dashboard, scores, analytics, training plans, AI chat, and nutrition tracking are all functional.
Things may change — Score weights, UI layouts, and API responses may be adjusted as we gather feedback.
Bugs are expected — If you find one, we want to hear about it (see below).
Data is real — Your data is stored in production infrastructure, backed up, and treated as permanent. We will not wipe beta data.

Frequently asked questions

How much does Omnio cost?

Pricing will be announced before general availability. Beta users will receive advance notice and a loyalty discount.

Which devices are supported?

Cloud-synced: Oura Ring (Gen 2/3), Garmin (all models with Garmin Connect), and Whoop (4.0+).

Direct BLE (via mobile app): Polar H10 chest strap, Polar Verity Sense optical sensor, Muse S (Gen 2) EEG headband, and any generic Bluetooth heart rate monitor. BLE devices connect directly to your phone — no cloud account required.

Can I use multiple devices at once?

Yes. Omnio merges data from all connected devices. When multiple cloud devices report the same metric (e.g. resting heart rate), Omnio uses a source priority system: Oura > Garmin > Whoop. BLE devices stream in real-time and can be used alongside cloud-synced devices. You can even connect multiple BLE devices simultaneously (e.g. Polar H10 + Muse S for combined HR/HRV + EEG monitoring). You can see which source is providing each metric on the dashboard tiles.

How are composite scores calculated?

Each composite score (Sleep, Readiness, Activity, etc.) is a weighted average of its input metrics, with weights based on published research. Every input has a citation. See the Dashboard Glossary for full details.

Scores use personal baselines where possible — your trends are compared against your own 30-day rolling average, not population averages.

Why doesn’t my calorie target change when I work out today?

Because the science says it shouldn’t. Omnio’s adaptive calorie target is driven by a 14-day rolling average of your training load, not today’s session. A single workout won’t move the number — but a sustained shift (starting a training block, a deload week, adding a second daily session) will nudge the target up or down over the following week or two.

This is deliberate. Other apps refund today’s workout calories in real time, and it sounds nice, but three things go wrong:

Wearable calorie estimates are noisy. Validation studies (Shcherbina 2017; Fuller 2020) show wrist-worn devices miss exercise energy expenditure by 27–93%. Eating back a device-reported “500 kcal burned” figure is a well-documented way to stall on goals.
Your body compensates. The constrained-TDEE model (Pontzer) shows humans drop spontaneous activity (NEAT) after hard sessions — so a workout that “burns 500 kcal” often only adds ~150–300 kcal to true 24-hour expenditure.
Weight change is the ground truth. Omnio fits your TDEE from what actually happened to your body given what you actually ate (the energy-balance method used in NIH body-composition models). A trailing window is how that math works — it can’t react to a single session any more than a thermometer can react to a single sip of water.

What should change on a heavy training day? Carbs and protein, not total calories. The sports-nutrition literature (Impey/Areta/Burke “fuel for the work required”) supports periodising carbohydrate intake session-by-session while keeping protein steady and letting fat flex. Calorie-periodisation is a later roadmap item — calorie targets stay stable so the underlying TDEE model can actually learn.

What if I’m untrained and just starting? Same answer, more so. The first few sessions are small, noisy, and mostly absorbed by NEAT compensation. Keep logging — the target will move as your new baseline builds into the 14-day window.

Is my data shared with other users?

No. All data is fully isolated per user. There is no shared data pool, leaderboard, or anonymised aggregate.

Can I export my data?

Currently you can export AI chat conversations (Markdown, JSON, or plain text). Full data export (all metrics, scores, and training history) is planned for general availability.

Can I delete my account?

Yes. Email [email protected] to request full account deletion. This removes all stored data including metrics, training plans, chat history, and credentials.

Known limitations

Sync delays

Wearable data arrives from cloud APIs (Oura Cloud, Garmin Connect, Whoop). There is typically a 1–4 hour delay between your device uploading data and Omnio receiving it. Oura webhook support reduces this to minutes.

Garmin re-authentication

Garmin session tokens can expire, requiring you to re-enter your credentials. This is a limitation of Garmin’s lack of a public OAuth API. We’re monitoring for improvements on Garmin’s side.

Composite scores need minimum data

Each composite score has a minimum confidence threshold (typically 30–40% of input weights must have data). If you’ve just connected and only have partial data, some scores will show ”—” until enough data accumulates.

Training plan — rotation-based, not calendar-based

Training plans use a rotation system (e.g. Push → Pull → Legs → repeat) rather than fixed calendar days. This is intentional — it means missed days don’t throw off your plan. But it also means you can’t pin workouts to specific days of the week yet.

AI chat daily limits

The AI health coach has a daily message limit (currently 30 messages per day) to manage costs. Tool calls (when the AI queries your data) count against a separate limit (90 per day).

Mobile app — beta quality

The mobile app (React Native / Expo) is functional but still being polished. Some screens may have layout quirks on certain device sizes. The web dashboard is the more mature interface during beta.

MyFitnessPal connections use browser cookies, which expire periodically. You’ll need to reconnect when this happens. We’re working on a more permanent solution.

Bloodwork and DEXA — manual upload only

Blood biomarker and DEXA body composition data must be manually uploaded via CSV. There is no automatic integration with lab providers yet.

Reporting bugs

Found something broken? We’d love to know:

Email — Send details to [email protected] with:
- What you were doing
- What you expected to happen
- What actually happened
- Screenshots if applicable
- Your browser/device info
Be specific — “The dashboard is broken” is hard to debug. “The sleep score shows 0 but Oura shows 85, and my account was connected yesterday” is perfect.

We read every report and typically respond within 24 hours.