Important news concerning our digital services

valdis830

Well, I correct! Paperweight for the use that I give to this type of devices, slow and obsolete for me. Most frequently used Apps are no longer compatible for use. Then because I want something that only technically is working. This about the iphone.

@Dimitrios-Kanellopoulos I agree that one company is not obliged to support every device for ever.
Maybe there is some other companies that do though. And support even 8 year old devices just fine (forerunner 210).
Sure, suunto made a business decision. This is just business. No hard feelings. But honestly, did anyone expected the end users to applaud this?
I am eagerly awaiting for a suunto survey…

andrejfit

I appreciate that Suunto is doing such communication quite long time before that thing will happened.

Dimitrios Kanellopoulos

@Yannis-Belouris We have > 1.5y to go and get all those goodies you mentioned (MC vs SA).

I do understand your points and they are already transferred.

Dimitrios Kanellopoulos

@Yannis-Belouris Nope I don’t think these news were good news to anyone invested on MC. That is clear.

Robert Rundqvist

@Dimitrios-Kanellopoulos said in Important news concerning our digital services:

@Robert-Rundqvist that what exactly is your problem or asking? I am a bit confused here.
Would it be nice @cosmecosta as well, to have a service to service integration or parsing of all routes?

@Robert-Rundqvist with the Suunto app, you can keep copies on the icloud or drive of your GPX routes and open then on demand with the app.

But then I will have to have a dropbox/Icloud/drive file catalogue of GPX routes which is an entirely different thing from having a previewable track catalogue online on Movescount. Which I then have to upload/open with the app and then sync to the watch.

I think the difference is rather big. Have I missed something?

Dimitrios Kanellopoulos

@Yannis-Belouris However, as @andrejfit said it’s quite a move to announce this >1.5y before this will happen. There is plenty of time for communication and changes. That is the whole point of this happening now 1.5y and more before it actually happens

valdis830

@andrejfit said in Important news concerning our digital services:

I appreciate that Suunto is doing such communication quite long time before that thing will happened.

Yes, is cool! And at no time is mentioned that it will not be possible to use it. It´s obvious that with SuuntoApp no.

pcjmfranken

@andrejfit While I’m getting a bit riled up about these bad decisions, I do also appreciate the fact that it’s being communicated early and that @Dimitrios-Kanellopoulos is actively processing feedback and replying.

Dimitrios Kanellopoulos

@Robert-Rundqvist said in Important news concerning our digital services:

@Dimitrios-Kanellopoulos said in Important news concerning our digital services:

@Robert-Rundqvist that what exactly is your problem or asking? I am a bit confused here.
Would it be nice @cosmecosta as well, to have a service to service integration or parsing of all routes?

@Robert-Rundqvist with the Suunto app, you can keep copies on the icloud or drive of your GPX routes and open then on demand with the app.

But then I will have to have a dropbox/Icloud/drive file catalogue of GPX routes which is an entirely different thing from having a previewable track catalogue online on Movescount. Which I then have to upload/open with the app and then sync to the watch.

I think the difference is rather big. Have I missed something?

So to understand your blocker atm. You use movescount because you have one place that your have routes collected and you prefer to only use WEB for route creation.

What stops you from importing these routes to SA now , via any feasible way, so you can use them, and edit / import export/ on any other service? In the future you will be even able to share those. Is this such a big deal for you? I am not arguing but rather trying to understand 100%. That is because atm from this announcement, routes is the least worry imo, and partially it’s a feature well done in SA.

@Dimitrios-Kanellopoulos And this is why we are voicing our concerns. The lower cost option was to not bother commenting at all.

Dimitrios Kanellopoulos

@Tobias-F said in Important news concerning our digital services:

@valdis830 said in Important news concerning our digital services:

I have iPhone 3, 4, 5 at home

your iphone are still working fine as standalone unit, with today’s announcement Suunto Ambit1/2, T3/4/6 Series, GPS trackpods are not longer working after 2020 because you need movecount.com mandatory to e.g. to add POD’s, adjust your bodymetrics, switch beween recording intervals or alter your sportmodes, so it’s a bit different here, Suunto is rendering these perfectly working devices obsolete by these lunatic change of the software platform without proper backwards compatibility

is that really the truth? Doesn’t your ambit work as a standalone as well and has many of these configs already in the watch available?

pcjmfranken

@Dimitrios-Kanellopoulos You can still use older iPhones to call, send and receive messages, use apps, use navigation, browse the web, pretty much anything you could do before.

After shutting down Movescount, I can no longer use my Ambit 2 for 80% of the things I use it for currently. Recording my moves is not really useful when there’s no way to look at them later. And not being able to plan routes beforehand makes it useless as a GPS device as well.

So I do agree with @Tobias-F

Dimitrios Kanellopoulos

@pcjmfranken I will withdraw my self from this argument (old phone experience) vs the ambits, as I better understand your point regarding the Ambit. But as an ex iphone 4 user till some months ago, I d have sincerely to argue that you can use that device to proper browse the web or even perform an Auth or navigate. Perhaps its the perpective or that apple slows down prev devices. In any case it’s a different subject that wont add value in this conversion from what I see. Lets focus on Ambits and their support.

Perhaps btw this helps to take a look at http://openambit.org/

Alex Nedovizii

After all, pretty sure there are lots of software developers around. Make A2 / Movescount thing open-source and that should do no pain and no money supporting it.

Dimitrios Kanellopoulos

@Alex-Nedovizii just posted about a possible solution http://openambit.org/

Alex Nedovizii

@Dimitrios-Kanellopoulos thank you, haven’t mentioned it. Sorry! This is at least something

Dimitrios Kanellopoulos

@Alex-Nedovizii Just to be clear. I DO UNDERSTAND that this is bad NEWS for the AMBIT2 users (the most + others) and I have no intension to smoothen this by posting something like: Oh look you can sync with that thing (http://openambit.org/).

I just post this from a personal perspective, as if I was an ambit user, perhaps after this news I would definitely try to see what I can do in regards to other SW for sync and getting my data out.

@Dimitrios-Kanellopoulos said in Important news concerning our digital services:

is that really the truth?

think that will be the dead end then for these watches, majority of setting on the tseries and early ambits (non BT) can only be adjusted via the movescount.com connection e.g. the POD’s can only be paired in the watch but can’t be activated for a particular sportmode, compass declination, bike pod calibration factors, gps accuracy levels, resting HR from bodymetrics … all of them come from a movescount sync only so over time these non ‘supported watches’ will get stuck with last settings somewhere from 2020 then…

Robert Rundqvist

@Dimitrios-Kanellopoulos said in Important news concerning our digital services:

So to understand your blocker atm. You use movescount because you have one place that your have routes collected and you prefer to only use WEB for route creation.

What stops you from importing these routes to SA now , via any feasible way, so you can use them, and edit / import export/ on any other service? In the future you will be even able to share those. Is this such a big deal for you? I am not arguing but rather trying to understand 100%. That is because atm from this announcement, routes is the least worry imo, and partially it’s a feature well done in SA.

Assume then my main route storage is SA - as there is no web interface in SA i cannot preview/edit/update them other than by either doing it on the phone (not feasible with detailed tracks required small fiddly changes) or by previewing in SA, exporting it to other platform, editing and then reimporting it.

If my main storage is elsewhere I loose the connection to the watch - I will have to export the route to GPX and then import into SA and then sync to wath. I actually think that is messy.

I either loose the quick load into watch or the workable catalogue.