Fitbit Inspire vs Garmin Forerunner 35

Now most smartwatches and wearables all have a lot of trouble being able to get really good accurate sleep measurements and while the Inspire 3 seems ...

Well, we're pretty much all my workout gear. The risk based heart monitor to me was a major selling feature. I want to be able to learn the maximum I ...

Notifications for texts and calls works fine. I work in EMS and mainly wanted to track my erratic sleep patterns and recieve notifications that I would otherwise miss with my phone in my pocket. I had high expectations I suppose.

What I don't like: ------------------ Phone integration for text and call notifications is spotty. Sometimes they work and sometimes they don't. It's a nice feature when it works. The phone downloads slowly but reliably to my Moto G7 Power

I also like that it comes with an always-on functionality so you can conveniently check the time at a glance as needed, although this feature tends to...

While I have found getting these alerts on my wrist pretty useful, this particular feature falls short of what the Pebble offered. There's no queue or timeline for reviewing notifications as there is on the Pebble and I find I miss the ability to simply scroll back through previous alerts. BATTERY LIFE The Forerunner 35's battery life is outstanding. I get between 8 and 10 days between charges, and a full charge takes only a few hours

The two sides act as a capacitor button and you can press them. Tapping them will always take you to the home screen or wake up the device. I like thi...

The first of the three times I got up to pee the Garmin showed that my ARHR had by that time dropped to 44, indicating that even though customer service told me that ARHR is an average over the last 7 sleep periods, my ARHR when I went to bed was close to 44 - which tracks with readings of the previous night, which also dropped intranight to 44. However, last night, except for those 4-5 brief intervals, which totaled about 10 minutes across the duration of my 6:30 sleep period, the graph of my HR shows a resting pulse that ranged from 34-44, with the average for the night being about 40. Yet at the end of my sleep period my ARHR had gone back up to 45! How did customer service explain this anomaly? Apparently the device ignores any resting pulses below 40 as artifacts, and since my RP was in the 30's for about an hour and a half, and since this wasn't even counted in averaging over the night (which gave more weight to the brief periods when my RP was in the high 40s and 50s) there was no drop in my ARHR, and in fact, over the last 6 months I've only briefly ever gotten it down to 44, even though my actual RP for the night is typically around 10-42, except on the nights after intense training sessions. Despite these evident software design flaws, my overall impression of Garmin, and even of the Forerunner 35, is positive