Coros Apex vs Garmin Forerunner 35

When setting up the Apex, the app asks you to select your training level (light, moderate, or hard), and set your daily calorie and exercise goals. I’m an average runner at best, so I selected the light training level, and went with the default recommendations of 153 calories and 39 minutes of exercise. If you find your exercise goals too easy, you can change them in the app. When you meet your daily goal, the Apex vibrates and shows a congratulatory message on its screen

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 ...

For those thinking that perhaps the Coros has a hardware issue, I should note that I had Bluetooth issues on the Pace 2 in many of the similar ways. And for those thinking it’s my phone, I had the same issue with my iPhone 11 and the Pace 2 as well. This is either the Bluetooth stack on their devices, or a poor handling of the Bluetooth API interactions on iOS. As I finally finished my customization (new watch face, workout screen modifications [data fields]), I was able to finally start putting the Apex Pro through it’s paces

95 at Fitbit)(Opens in a new window) , which gives you the option to send a canned response, emoji, or voice-to-text reply.

I actually give Fitbit the win on both mobile and website interfaces. I find the dark theme and low contrast text on the mobile app hard to read. I don't like that some screens/views require rotating the phone. And, it's just hard to see some of the data I want to see, like HR during specific parts of a workout

Are you a runner looking to take training to the next level, but can't afford a really pricey device? Wondering why in the world you'd even need one? I was in your shoes! As an activity tracker, the Forerunner 35 is very nice. I give it 3 stars because many of the features that a runner would use don't work, and I feel it's deceptive to sell a device with these features when they're not really usable for training. Essentially, this is a good activity tracker posing (ineffectively) as a training tool. Many reviewers mention that the Forerunner 35 isn't for "serious runners", and I took that to mean that they believe "serious runners" need all the complexity of a very expensive watch

I'm in love with my Coros Apex. Got it for $300 on sale. I seriously do not think there is a better deal for a watch. To get a comparable Garmin I'd have to spend $650

Garmin won't be able to sell the Forerunner 35 for $200 for too long. $150 seems like a better price point. I'm sure a Forerunner 35-level watch will be selling for only $100 or so in a couple more years. The Forerunner 35 wears pretty nicely

I almost forgot I had it on at times. The battery life is the selling point of this watch (and frankly, all Coros products). A bit better than what I get on my Fenix 6X. The trade-off in software and lack of data ultimately had me stick with Garmin though

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

I have had a 245 for 2 years and it’s pretty dope. I really can’t see myself upgrading to a different running watch (though having Garmin Pay would be nice).

I used the quick-release wristband because I would go back and forth between my road bike. I don't think I'll ever rely on it again because this is the second time it's disconnected accidentally, and certainly the last time since there's no hope of finding it along the 10 mile trail of rock and mud.

I only use the text & call notifications because everything else was just overwhelming/obnoxious. That's also because my Pixel was updated & the "new & improves bubbles" turned my notifications to shit.

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

So I've recently update the firmware of my Coros Apex and updated the app. After that the watch was unpaired from my phone and I can't pair it. I've tried everything. I've reset all network connection and cache on my phone, restarted my phone and watch, reset my watch, but still nothing

SUMMARY As disappointed as I am in the Apple Watch as a running watch, I'm not switching to the Garmin until they address at least the first two items under CONS above. I feel certain the CONS I mention above are purely in the software, so hopefully they'll enhance some of those capabilities in a future update. If not, maybe Garmin needs to release a Forerunner 40 that handles those features better. The higher end Garmins may already cover those complaints, but they're too expensive for a running watch and not sufficiently capable for a smart watch

And, it's just hard to see some of the data I want to see, like HR during specific parts of a workout. The iPhone app interface is why I gave it a 4 star instead of 5 star and I'd probably only deduct half a start if that were possible.

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

No complaints. It is comfortable to ware all day and night. It is very light and does not feel thick in the wrist. The Band: The band is also very light and comfortable

I think as long as you can run comfortably at a conversational pace, your HR shouldn't matter too much. That's not to say you shouldn't strive to get better at running, but there are so many more metrics than just HR to tell you if you're on the right path. Happy running :)