New UI hickups

[Jojo]

Hello ABRP

 

Your new UI is...ok, but very buggy. Do you use this for some minutes? I encountered several problems within 10min of use.

First, I use it on a smartphone in Chrome and Fermata Auto. Why Fermata? Because this way I can have all the planning and the burn down chart in Android Auto (Skoda Enyaq). The App with AA is still useless for me.

1. How to select a destination from the map. Right Click, ok. And on a smartphone?

2. Scrolling through a plan is messed up. You put your finger on the display to start scrolling and it jumps to another place randomly. In Chrome and Fermata (desktop mode)

Difficult to see in the video.

 

3. How to come back from the destination input screen without inputting something?

X doesn't work. Back doesn't work. If I press back several times, it jumps back in browser history.

 

 

4. Input on-screen in the car doesn't work in Fermata. Text I type always disappears again.

Video will follow.

 

5. Scrolling in AA Fermata in the saved Destinations view doesn't work either.

Video will follow.

 

I think the new UI is going in the right direction in terms of simplification. To have the settings always in the same spot is great.

 

Thanks

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

[Bill N]

Seconded - can we revert to the old one until bugs are fixed. Did it go through beta testing?

Kinda hate to say it, but I’m not really sure what the changes have added - I’m struggling to immediately see anything where I think “oh yes, this is so much better now”. Sorry.

[Jojo]

Come on guys.

The slow chargers are not displayed, despite they are choosen and selected on street level. Tried with Chrome and Fermata.

Start creating a test strategy, create a test plan and stick to it! People are paying for your service!

[green light]

First impression: much better than old. But then I started planning a route and found several errors, as others here, too.

If you want to change the departure time (just time, not date), you can't without changing day.

So the same issues that we had when the other new UI came up: not tested, not working. But this time, not for free. I'm tired of reporting bugs that must not happen every time a new release is deployed.

 

[Jojo]

Hello ABRP

Are you there?

Your new interface is not working!!!

I still can't select a via point on a touchscreen device.

I still can't input time/SoC or anything in the waypoint options

Still the scrolling is messed up

Still the input of destinations cannot be exited

I tried Chrome and Fermata in Android. Same bugs.

Are you working on your customer complaints or just ignoring us?

 

 

[Samuel-ABRP]

Please use the new feedback functionality in the app.

We are also constantly working on improving the new UI so always try the latest version available.

[Samuel-ABRP]

Btw what is this fermata? I don't think ABRP via Fermata is supported if that is some kind of screen mirroring.

Many of the things you mentioned work pretty well, for example long click on map shows the add waypoint screen.

[Bill N]

We desperately need waypoint numbering / lettering please - like Google maps.

 

[Samuel-ABRP]

Please open a feature request for that via feedback in new ui. You will get to the new issue/feature board where you can add these requests.

[Jojo]

Yes, Fermata is a browser/media player, which can be mirrored via AA.

The behaviour of the UI is exactly the same like the normal Chrome browser under Android.

Long press doesn't work. Please show a video of this with Android Chrome browser. 

Thanks

[Samuel-ABRP]

Please use the app and not the browser on android. The browser version also works partially on Android but is mainly intended to be used by desktop PCs. The app is more optimized to be used with mobile devices.

We could however check if we can add the same functionality on mobile web, which then however would be treated as a feature request.

[Jojo]

Hello Samuel

First, thanks for your answer.

I would love to use the app, but the app is useless with AA in the car.

Feature number 1 of ABRP in driving mode is the burn down chart... which the app doesn't show in AA. 

[Samuel-ABRP]

The burn down is not as important for driving as you think. It definitely is a useful feature but the most important for driving is the arrival SoC which is also displayed in AA. I use AA for almost a year now and in the beginning it was a bit strange to drive without the burndown, but it is actually not really needed. You just need to check, that the arrival SoC does not change too much into dangerous regions. So if the SoC goes a bit below your expected arrival SoC you drive slower, if it goes way above you can drive faster. There is really not much of a difference in the end.

That said I unfortunately have to tell you that the SoC burndown will most likely not come to AA as google is very restrictive here.

If you still want to use the app instead I would recommend to use it via phone app and screen.

[Jojo]

Hello Samuel

Thanks for explanation.

I maybe have to try it out. If the shown arrival SoC is always the current estimated one, wouldn't it be helpful to show it in green or red in comparison to the planned one? Otherwise the reference is missing, which I would see in the burn down as well.

The bigger problem with AA is, that it pulls focus, if you use it.

I use the in car Navi because of the better in car integration, augmented reality HUD....

If I use ABRP App with AA it stops that navigation. So I can not use ABRP AA in parallel with in car Navi.

And to be honest, ABRP Navi is not in the stage to use it exclusively as the one navigation tool.

If we would be able to deactivate the "active" navigation, just showing SoC and the route with the stops, it would be fine.

Thanks

 

[Bill N]

11 hours ago, Jojo said:

Hello Samuel

Thanks for explanation.

I maybe have to try it out. If the shown arrival SoC is always the current estimated one, wouldn't it be helpful to show it in green or red in comparison to the planned one? Otherwise the reference is missing, which I would see in the burn down as well.

The bigger problem with AA is, that it pulls focus, if you use it.

I use the in car Navi because of the better in car integration, augmented reality HUD....

If I use ABRP App with AA it stops that navigation. So I can not use ABRP AA in parallel with in car Navi.

And to be honest, ABRP Navi is not in the stage to use it exclusively as the one navigation tool.

If we would be able to deactivate the "active" navigation, just showing SoC and the route with the stops, it would be fine.

Thanks

 

Try experimenting with the order in which you activate the two navigations.
 

 

 

[Jojo]

No, in each order, the latest running Navi kills the one before.

 

[Samuel-ABRP]

Earlier there was the requirement from google to stop navigation if another navigation app starts. Not sure if that is still the same. Could check that later.

 

In future please use the feedback functionality in the app as there will be no official support anymore via forums but that will be announced seperately as well soon.