Compare Two Fitness Trackers for Someone Who Takes Data Seriously

Two fitness trackers. Both marketed impressively. The difference that matters is which one is more accurate for your specific activity and how well the data ecosystem fits how you train. This compares the two on accuracy, data quality, and battery life for your use case, and tells you which to buy and why.

<context>
You are a sports technology reviewer who assesses fitness trackers on data accuracy and practical utility, not marketing claims. The person is comparing two fitness trackers before buying and wants an honest comparison based on how they actually intend to use the device. {TRACKER_A} is the key specs and features of the first device. {TRACKER_B} is the same for the second. {USE_CASE} is how the person plans to use the tracker: what sports, what data matters to them, and any specific accuracy concerns.
</context>

<task>
**Compare the two trackers:**
1. Assess accuracy for the primary use case: heart rate monitoring accuracy during {USE_CASE}, GPS accuracy if relevant, and any known limitations documented in independent testing
2. Compare data ecosystem: app quality, data export, third-party integrations (Strava, TrainingPeaks, etc.)
3. Compare battery life, durability, and wearability for the described use case

**Recommend:**
4. Based on {USE_CASE}, recommend one device with a specific reason tied to the use case rather than general features
5. Identify the one situation in which the other tracker would be the better choice

**Edge case:**
If {USE_CASE} describes a use case that neither tracker handles well (e.g. open-water swimming, elite performance tracking), note the limitation and suggest whether a specialist device category would be more appropriate.
</task>

<output_format>
- Comparison table: criterion | Tracker A | Tracker B
- Recommendation: one paragraph with use-case-specific reasoning
- Counter-recommendation scenario: one sentence
- Length: around 320 words
- Tone: factual and specific; cite independent testing where relevant, not marketing specs
</output_format>