S9 Baro Wishlist
-
@General_Witt is a bug
-
@silentvoyager I might take the chance to introduce you to our UX that are endurance athletes. Eveyone has an opinion but these speculations in our forums I wont tolerate
In regards:
Yeah, the UX was clearly designed by someone who wasn’t a heavy user of previous models of Suunto watches and not an endurance athlete themselve.
Yellow card
-
@Dimitrios-Kanellopoulos said in S9 Baro Wishlist:
@silentvoyager I might take the chance to introduce you to our UX that are endurance athletes. Eveyone has an opinion but these speculations in our forums I wont tolerate
In regards:
Yeah, the UX was clearly designed by someone who wasn’t a heavy user of previous models of Suunto watches and not an endurance athlete themselve.
Yellow card
OK, point taken. I apologize. I still think Ambit UX is more functional.
-
@silentvoyager no problem its not about the apology it’s about keeping a fair spirit here.
I do understand that the UX can be better, I dont argue…
-
@silentvoyager said in S9 Baro Wishlist:
@General_Witt said in S9 Baro Wishlist:
@stromdiddily Exactly, I cannot understand why the breadcrumb is mandatory and not automatically deactivated for all indoor sports, like indoor cycling. It has discouraged me from creating custom sport modes, I still use the factory ones that have data fields I’m not interested in.
Yeah, the UX was clearly designed by someone who wasn’t a heavy user of previous models of Suunto watches and not an endurance athlete themselve.
Hmmm. I did not design any of this but I am certainly an endurance athlete an like the UI a lot. The breadcrumb screen in custom indoor modes is a bug. I disagree with you on the rest
-
@Brad_Olwin said in S9 Baro Wishlist:
Hmmm. I did not design any of this but I am certainly an endurance athlete an like the UI a lot. The breadcrumb screen in custom indoor modes is a bug. I disagree with you on the rest
It is OK to disagree, I agree to disagree. This new UX was designed with touch first in mind - everything is big and information density is generally low, for example often we see a screen with just one large number on it, and to see another number you have to swipe or touch the screen. But touch just doesn’t work well in outdoors environment when it may rain or your fingers may be frozen or sweaty, or dirty, or you may wear gloves. Suunto later recognized that and now disables touch by default during exercises, but the touch optimized UX remains. Second, because of the touch-first design only 3 hardware buttons remained, and all of them are pretty much reserved during an exercise - one for stop/resume, another for lap, and the middle one for changing through the screens. That makes it very difficult to implement any operations on the watch with just buttons beyond bare basics. There several workarounds in Spartan UX, but they are inconsistent. For example, context menu is usually invoked via the middle button long press, but on mandatory navigation screen - lower button is used. All those silly workaround to trigger backlight is another example. The lack of the “view” button makes it pretty much impossible to rotate through alternative views like changing navigation views without piling all possible navigation view in the main rotation of displays (that’s what Spartan UX does by adding route profile).
-
@silentvoyager said in S9 Baro Wishlist:
@Brad_Olwin said in S9 Baro Wishlist:
Hmmm. I did not design any of this but I am certainly an endurance athlete an like the UI a lot. The breadcrumb screen in custom indoor modes is a bug. I disagree with you on the rest
It is OK to disagree, I agree to disagree. This new UX was designed with touch first in mind - everything is big and information density is generally low, for example often we see a screen with just one large number on it, and to see another number you have to swipe or touch the screen. But touch just doesn’t work well in outdoors environment when it may rain or your fingers may be frozen or sweaty, or dirty, or you may wear gloves. Suunto later recognized that and now disables touch by default during exercises, but the touch optimized UX remains. Second, because of the touch-first design only 3 hardware buttons remained, and all of them are pretty much reserved during an exercise - one for stop/resume, another for lap, and the middle one for changing through the screens. That makes it very difficult to implement any operations on the watch with just buttons beyond bare basics. There several workarounds in Spartan UX, but they are inconsistent. For example, context menu is usually invoked via the middle button long press, but on mandatory navigation screen - lower button is used. All those silly workaround to trigger backlight is another example. The lack of the “view” button makes it pretty much impossible to rotate through alternative views like changing navigation views without piling all possible navigation view in the main rotation of displays (that’s what Spartan UX does by adding route profile).
Yes we disagree. I never need more than 4 fields on a screen and often use 3. I can get by with 1 screen of 4 fields, the Nav screen and altitude profile when I run with routes, especially races. I typically will lock the screen. All I need now is for waypoints to work like they used to. I cannot reliably see more than 4 fields and the backlight works great at night when my screen is locked…I just don’t push a lot of buttons when running or SkiMo and love the UI.
-
@Brad_Olwin derailing the thread a bit here but what data fields do you use for races?
-
@stromdiddily I use the outer ring to check either HR or power so I don’t need that field (I know my zones). The altitude and ascent show on the route altitude profile so I don’t need that field either. Just 3 fields, Avg Pace, Duration, Distance. If my ultra is shorter than 25h then I might add another screen with ETE and ETA information. That is it. If I need lap info I can include that but I usually do not as I have a laminated card with aid stations/expected times and cutoffs on it.
-
That list is right on – particularly the first 3 items and the comment about more/customizable watch faces. Most of that seems pretty doable in my opinion, and given some time I think we will see the majority of these things come to be.
I gotta say, I’m digging the battery life tho during runs tho, its fantastic! Weird to me how much it takes up during a normal day without any activity (seems like 10-12% for me). Maybe that is reasonable, I’m not sure, but it seems if a watch can last 24 hrs in GPS mode with HR, etc, day to day might take up less battery overall?
Keep it coming tho! There seems to be a great base here, excited to see what’s to come.
-
Bumped and edited based on feedback in the thread
@Dimitrios-Kanellopoulos - is there a better place for a list like this? Or a place for consolidated hardware feedback in general?
-
@Brad_Olwin said in S9 Baro Wishlist:
The altitude and ascent show on the route altitude profile
Route altitude profile shows estimated remaining ascent according to your position on the route.
-
- A POI interface on the SA application
-
@AnthonyB said in S9 Baro Wishlist:
- A POI interface on the SA application
Hey now, don’t be hijacking my watch thread w app features.
But also…yeah need that feature too
-
This post is deleted! -
This post is deleted! -
This post is deleted! -
- Create a workout plan and workout schedule.
-
@stromdiddily said in S9 Baro Wishlist:
More watch faces and/or customizable fields
Yes!, would be excellent select what info I would like display on main screen. I have a super-device but can´t see my preferred information without do a “clic”
A nice small graphic of the barometer with evolution of the last hours, temperature, altitude, etc.
Some old Casio or Timex watchs have more info on main screen…
-
This post is deleted!
