The app has a lot of potential but a lot of flaws

The app has a lot of potential but a lot of flaws and I am using since almost a year and I see little progress. Among the most annoying things:

• I have set for long trips that I have at least 40% SoC at destination. This is becoming a problem for shorter trips starting around 40% SoC: even if the trip is 20 Km long, the app still tries to reroute me to a public charging station - and the app does not offer a simple “ignore the charging stopover” button.

• If I ignore a proposed charging stopover and drive further toward the destination, the app crashes.

• The app does not read consistently the correct SoC from the car (or the app shows a different SoC than the car), independent if it reads that via Enode or via the ODB. Is not a big difference, ABRP shows something between 1 and 4% less SoC, but that is messing up the planning for stop overs.

• It does not consider the traffic on the road (or you are using a very unreliable source of information): I am guided to follow roads that are congested and put straight in traffic jams. On Google map, the traffic jams are there, but it looks like you use a different source of information.

• The app stops working if the phone has no data coverage (e.g. when I drive across border, it takes a minute or so, until the phone selects a mobile network in the new country). The fact that the app crashes, is an issue, especially if I need to change the road before the phone have managed to select the network, I manage to restart the app on the phone, reselect the destination… That all take time and is caused by a bug in your app.

• When planning a new route, the ABRP estimated SoC as destination is far from reality even for 150 km trips, starting with 95% SoC - ABRP estimated that I should have 52% SoC (43% battery usage), while in reality I will have 68-69% (27% battery used in reality) - so, your algorithms are 60% off…