Very disappointed with Next.

b0hd1

@Con-Hennekens Without fear of sounding pedantic, I can say that I consider myself an advanced user of Mra&next. That being said, I understand the sentiment of my fellow member @Maicro (one of the 500 members of my group), who, like many others in my group, is looking to ride the motorcycle without worries. And Next, despite my passion for it, doesn't perform well for the average user.
These days, I have been able to test it intensively for a week and over 3000kms, and it's challenging for me to fully defend it in my group.
But we continue testing to improve it. Thanks @Corjan-Meijerink for your work!!!

Michel van Hagen MRA-Founder

@b0hd1 Can you tell why? We also drive many kilometers ourselves, I drove the Iron Curtain Trail season 2023 myself together with Serge. Serge with an android device and I with an iPhone in combination with Apple CarPlay and we have really not encountered any problems in our almost 6000 km! And this does not only apply to us, but to many users, hence the high review score.

b0hd1

Hello @Michel-van-Hagen-MRA-Founder
Nothing serious but rather inconvenient, like the gray screen or having to log in again with some frequency.

There are also complaints about the automatic point jumping, excessive battery consumption, and other issues that, for example, don't bother me, but they do bother the "average" user.

But you know I'm a loyal advocate and fan of the system. So, we'll keep testing diligently!

Maicro

@Tom-Cat said in Very disappointed with Next.:

I am with you @Maicro. After my experience with MRA Next this past weekend on a 3-day trip I am abandoning Next at least until the next update. I have had multiple issues during my last three uses all while trying various tips and tricks provided here. I was really hoping Next would enable me to leave my TomTom at home but for now it cannot.
I had to dig out my TomTom Rider 400 yesterday and get it updated and current after not using it for almost a year. This also means I need to install the accessory mounts onto my new motorcycle to support that device, something I was hoping to not have to do. I will also need to move my routes from the HERE maps back to TomTom which can be time consuming for some of my routes.
And before people start ripping me, I have a lifetime MRA membership for more than 10 years or at whatever point they started offering lifetime memberships. I also bought the MRA Next lifetime membership last year when the new development efforts were announced. I'm sure the team will get it to where they envision they want it to go but right now, it is not stable enough to be relied on regularly.

I'm sorry to read your words. In my biker club several users have reported the same problems. I am hopeful that they will fix it. In fact today I installed the new beta and it has worked better. Then I'll tell it in detail.

Thank you so much.

Maicro

@Corjan-Meijerink said in Very disappointed with Next.:

@Lynchy67 this update is now in Beta phase and will be released to the public next week

Indeed. Thank you. But there are other failures that persist and new ones that I have suffered today. Then I'll put it in detail.

Maicro

@Con-Hennekens said in Very disappointed with Next.:

@Tom-Cat said in Very disappointed with Next.:

but right now, it is not stable enough to be relied on regularly.

You forgot to add "for me" at that sentence . Many have navigated long multiday trips without really serious issues. I did so even in the early May version. Many have even thrown away or sold off their zumo's and TT riders and never looked back. I won't say I never have issues with the app, but they were always solvable or worked around.

OK. But that does not mean that we notify these problems so that, precisely, they can be solved.

Maicro

@Michel-van-Hagen-MRA-Founder Are you insinuating that I make up my problems?

I am here as a registered user after having paid my official license. My message is intended to help developers solve the problems we encounter.

If you are a crack programmer who makes everything perfect, it is easier for me to ignore all this and directly put negative reviews in the application stores and forums where I move instead of tolerating the impudence you just said in an attempt to help for me.

Tom Cat

@Con-Hennekens I did say "After my experience with MRA Next this past weekend..."

As I also said, I am not abandoning MRA. I do think they will get things sorted out over time and as I also mentioned I have been using them for more than a decade. Maybe I set my expectations to high for Next but for now it's not working for me in my usage scenario. Everyone has slightly different issues and it's almost impossible to test all scenarios between different phone manufacturers and models and vehicles with Android Auto or Car Play. For example, battery life is not an issue for me right now because I always keep my phone plugged in for Android Auto when riding.

My comments are not a dig at the MRA team, I'm confident things will get sorted out. I just bought a new motorcycle with Android auto so I never tested it during the beta period earlier this year. I will try again when 4.04 is realized to the public.

Maicro

@Tom-Cat said in Very disappointed with Next.:

@Con-Hennekens I did say "After my experience with MRA Next this past weekend..."

As I also said, I am not abandoning MRA. I do think they will get things sorted out over time and as I also mentioned I have been using them for more than a decade. Maybe I set my expectations to high for Next but for now it's not working for me in my usage scenario. Everyone has slightly different issues and it's almost impossible to test all scenarios between different phone manufacturers and models and vehicles with Android Auto or Car Play. For example, battery life is not an issue for me right now because I always keep my phone plugged in for Android Auto when riding.

My comments are not a dig at the MRA team, I'm confident things will get sorted out. I just bought a new motorcycle with Android auto so I never tested it during the beta period earlier this year. I will try again when 4.04 is realized to the public.

My comments are not intended to be indirect either, they simply help develop this application that I like so much. But after the "pearl" that @Michel-van-Hagen-MRA-Founder has dedicated to us, one seriously considers whether it is worth offering this type of help.

b0hd1

I believe that we are all here to collaborate and, under no circumstances, bother the Mra team. Each and every one of our 'complaints' is aimed at contributing to the improvement of what will undoubtedly be the best browser that exists. But if it has flaws, our duty is to comment.
Please, let no one be upset about it!

Maicro

Today I installed beta 4.0.4.

Communicate that it is much more stable. It has not crashed, rotated, or changed day or night modes.

They only remain a problem. There are route points that it continues without knowing that I pass them and forces me to return. I think, because I'm not sure, that it was at the first waypoint that I had given color and put an indicator -Warning- in MRA.

Now there is a new failure that before yesterday I did not suffer. With the JaxeADV controller, button 4, to jump to the selected waypoint in the points list, does not work.

And @Michel-van-Hagen-MRA-Founder, consider it a help for you to improve the product. It is not an empty criticism. I assure you that I am very interested in making Next work perfectly because I love its integration with MRA.

Corjan Meijerink

I do thank you all for the feedback and we consider everything in making the app perfect for everyone.
Adding features is ‘easy’ and important.
Fixing user issues that occur with individuals and are hard to reproduce for us is tedious.

Tedious is never fun but still crucial. Currently we are devoting around 60% of our time to improving general stability of the app core and thus also specifically the communication with CarPlay / Android Auto.

I have been chatting with @Maicro to get some detailed feedback and logs Yes, this will help with fixing issues.

The new 4.0.4 update with public release next week will already fix some frequent issues.

I will lock this thread now as enough has been said about the original topic. I’ll continue chatting with @Maicro about the encountered issues. If anyone here personally feels the need to chat with me, just do so

Thanks for all your contributions, all the time