YouTube Music not supported

Ironically I think Apple has a much better rep for UX than Garmin (and rightfully so). (I wrote this sentence before your latest comment.) I'm the first one to complain about Garmin UX, believe me. (I think they've improved a lot over the years tho.)

But Apple is probably happy to let the app dev take the blame for any weirdness in this case.

I have an 8 year old running pace calculator on my iphone which was never updated for the larger screens. It works great and its still the best pace calc on the store imo, even though it looks kinda weird (black borders on the top and bottom). I would've been mad if I couldn't use that app on my newer iphone.

But then again, I thought Apple took steps to hide apps from search results which haven't been updated in a while? I can still find the old app with a search, even on the web (so I'm not logged in and it's not tied to my device.)

If you want to stick with the architecture change and think if that doesn't change, then no reasons for require rebuild. But like others have already pointed out that the old Fenix and new Fenix has a lot of big changes.

And Garmin to require good UX, is not allowing to install the apps to whatever devices they make to see how it works is their decision and in their control. I don't see any problems there.

Probably the amount of users in Google's point of view is just tiny that they don't give it much priority and that's pretty much it. That is then on Google, not on Garmin, even you like to blame Garmin here, that they require too much from developer. 

For what I could blame Garmin is that if one can't really get SDK's before device releases for fear of leaks and such that it's pretty hard to developer to have the app to be there at the launch day, but very few users will get the devices in their hand on that day and then developers have plenty of time..

jmto said:

If you want to stick with the architecture change and think if that doesn't change, then no reasons for require rebuild. But like others have already pointed out that the old Fenix and new Fenix has a lot of big changes.

How much different is the Fenix 8 specs over the latest Epix?

jmto said:

For what I could blame Garmin is that if one can't really get SDK's before device releases for fear of leaks and such that it's pretty hard to developer to have the app to be there at the launch day, but very few users will get the devices in their hand on that day and then developers have plenty of time..

This is counter to Garmin wanting to create the best user experience.  Because I'd rather have a YT Music app that may not be perfect (which garmin seems fine releasing beta software on their new devices) than not have access to it at all.

My 'user experience' with this watch has been a bit meh, and there seems to be quite a bit of issues they were ok releasing with (at the firmware level).

Just an FYI, I ran a software QA department for a number of years, so I do in fact understand the SDLC involved here pretty extensively.  Not the Garmin/public specific stuff, but what should/shouldn't be 'passed' for go-live.

Put a business hat on then and consider that the immovable product release schedule (PR and marketing schedule, trade shows etc alignment), along with whatever position engineering found themselves in, might have forced the situation at product release. Don't know what business you were in, and the competitive landscape thereof, but sometimes one has little choice. 

I’m allso waiting for YouTube music to be available!!

No doubt, I definitely get it.  But why be "ok" with going live with unfinished firmware, but being so picky with the SDK/apps supported.  In both cases they are choosing the option which negatively impacts the user experience.

I have historically complained about how going live with a 99% working product late is better than going live with a 75% working product on-time.  Both suck, but all the industries have long since decided option 2 is the preferred.

jmto said:

FlowState said:

I have an 8 year old running pace calculator on my iphone which was never updated for the larger screens.

Pace+ ? At least in Android world that is a nice thing and yes, seems like it's abandoned but still works, but can't be found from Play Store. Has been just moving along with migrations from old phone to new one.

Pacey for iOS.

Judging from the Pace+ screenshots, Pacey is a bit simpler than Pace+ (it only has a pace calculator and splits page), but it has a few unique features that most other pace calculators don't seem to have:

- you can independently toggle units (km / miles) for any of the values (distance, time, pace, speed). This is useful for me as a Canadian since we use km, km/h and min/km, but we're close to America which uses miles. (And the mile is still common racing / training distance.)

- you choose one of the values to lock (distance, time, pace/speed), so that it's clear which value will be calculated when you change another value

Some other calculators have the inputs for the values on different pages than the actual calculator (e.g. when you tap on the pace value, you're taken to a different screen to actually enter the pace.) This just slows everything down for me.

And most or all of the other calculators seem to:

- not have the ability to independently toggle units (you can only set units in one place, and it affects all values).

- not have the ability to lock one of the values. they just guess which value to calculate (based on the the last 2 values you changed.)

While all of that may be simpler in a way, it's also less efficient (for me). Having said that, I recognize that something like Pacey probably isn't for everyone - it's probably more of a power user tool (simple in its own way, but with a slight learning curve due to the part where you lock one of the values), so I can see why some of the things it does haven't been widely copied.

Dallace said:

How much different is the Fenix 8 specs over the latest Epix?

Depends a lot on which Fenix 8 ;) 

Dallace said:

there seems to be quite a bit of issues they were ok releasing with (at the firmware level).

Nothing new there either. It's kind of beta tester experience of buying new Garmin straight from the launch, but like I don't see that as a argument that well if the firmware has issues, you should also be having apps that have issues? They can easily block the apps before they are tested and satisfactory working, but they need to release the watch at some point which is usually before the developers would want to release it. So here we are.

FlowState said:

Judging from the Pace+ screenshots, Pacey is a bit simpler than Pace+

It has a lot of features, but what I usually use it just to solve one of the tree from "Distance, Pace, Time". Unfortunately calculating these isn't so nice in the head as we have 60 seconds to a 1 minute..