Head to head
Chargemap or Drive Charge Eat: where they actually differ
Two products with different jobs. Chargemap is a roaming and payment product — its job is one account across many networks; Drive Charge Eat is a dedicated route planner — its job is deciding where you stop and for how long.
Where they differ
| Capability | Chargemap | Drive Charge Eat (our own app) |
|---|---|---|
| Plans a charging route | ◐ Partly | ● Yes |
| Adjusts for weather and temperature | – Unverified | ● Yes |
| Accounts for elevation | – Unverified | ● Yes |
| Preconditions the battery | ○ No | – Unverified |
| Turn-by-turn navigation | – Unverified | ● Yes |
| CarPlay or Android Auto | – Unverified | ◐ Partly |
| Pays for the charge | ● Yes | ○ No |
| Compares session prices | ◐ Partly | ○ No |
| Food, restrooms and facilities | – Unverified | ● Yes |
| Driver check-ins and reviews | ● Yes | – Unverified |
| Usable without paying | ● Yes | ○ No |
Where they agree
On the remaining 3 capabilities these two are recorded the same way. Rows where both are unverified are agreement about our own ignorance rather than about the products.
Which to choose
Choose Chargemap if you need to start and pay for charging in the app, driver check-ins from the last people there and something that costs nothing. Choose Drive Charge Eat if you need a planned charging route rather than a map of chargers, cold-weather range modelling, routing that knows the road climbs, turn-by-turn navigation rather than a hand-off and food and facilities where you stop. Price and platform decide the rest, and both are in the table on each product’s own page.
Or both
Most people end up with two of these — a router and either a payment card or the car’s own navigation for the last leg, which is the only thing that reliably preconditions the battery. Using one tool for everything is a preference, not a requirement.