It all started when I got tired of guessing the amount of money I had to bring on roadtrips. I took the #1 navigation app in the App Store and reimagined how Google might implement toll pricing transparency.
To begin, I asked the following questions:
- How many people were also running into this issue besides me?
- How popular was driving compared to other modes of transportation? Do people still drive long distance or do most people fly?
- What were pre-existing methodologies drivers used to calculate tolls?
- What apps and services were currently on the market addressing this issue?
Are road trips still a thing?
AAA did a study concluding that road trips have gained popularity as many people now value spending money on memories more than material items. Not only that, but driving is still the more practical option when traveling due to lower costs and less packing restrictions.
Background information about toll agencies
72% of the U.S. implement tolls. There are currently 17 total toll networks with the largest being E-Z Pass. States are increasingly using tolls to fund transportation improvements. The amount of the toll usually varies by vehicle type, weight, or number of axles, with freight trucks often charged higher rates than cars. The most common variable across all 17 toll networks is the number of axles. Most people drive 2-axle cars so that must be chosen as the default.
Tolls are used to fund the upkeep of the road system. When driving on unfamiliar routes however, drivers have no way to prepare to pay for tolls, some of which may be cash only.
What do people do now?
I decided to do some social listening and went on the world’s largest focus group: Reddit. I opened a post in r/roadtrip to ask what people usually do.
Many suggestions on Reddit mentioned they do the following:
- Plot route
- Identify tolling agency and facility
- Go to tolling website to see how much it costs
- Check to see if I get discounts with a transponder
- Add it all up
- Repeat 1x for trip back
A couple apps were mentioned, such as Toll Calc. Many of these resources either needed too much information (i.e. total weight of car) or calculated tolls on a static map. This meant I would have to switch back and forth between apps to drive and keep informed. Currently, all navigation apps provide users with the choice of either avoiding all tolls, or allowing all tolls. Beyond this, there’s no customization.
What does Google Maps do currently?
Within the app, I saw a couple key areas to improve.
- Issue 1: Make the toll icon more obvious
The current icon on iOS doesn't stand out enough to catch attention.
- Issue 2: Use a consistent icon
Switching between icons can be confusing and makes the user pause. Consistent associations allow for quicker mental processing.
- Issue 3: Indicate exactly where the tolls are
This is more helpful than making the user manually search in the directions list for where tolls show up on the road. If Google Maps can do that for car accidents (shown below), why not tolls?
- Toll calculations needed to exist in the Google Maps app
- Account for users with and without toll passes
- Indicate the route has a toll
- Provide cost transparency so that the user can make an informed decision
- Toll calculation had to be based on a common denominator amongst all toll agencies
What are the benefits of in-app toll calculations?
- Be aware of the costs and locations of all tolls on your current route.
- Compare and contrast routes based on toll costs.
- Avoid unnecessary or expensive routes.
- Add your transponder information for accurate toll estimation.
- The ability to prepare your toll money in advance.
Make the icon more obvious
The current icons for tolls are unclear and don't stand out. By redesigning the toll icon to be yellow with a dollar sign, the user can quickly identify any toll road that exists on their route.
Feedback from Redditors
One of the most common feedback I got was to be able to control time and cost.
“What if the user can set a minimum time the toll would save me?” “What if the user can set a maximum amount of money spent on a toll?
I initially tried to design a feature to control time versus cost payoff.
An example use case would be if a driver refused to pay $5 for a toll, but if the driver realized it would save them 30 - 60 minutes of driving, s/he would probably pay the $5. How can Google Maps show this? Can the driver place certain constraints for the app to populate this information?
In the end, I decided not to add this feature. Not only could it result in a null set, but hiding information would go against my original project goal of transparency. All options should be laid on the table for the driver to make an informed decision.
A network for all
After some feedback, an idea I played around with was improving the overall toll experience by implementing a third-party transponder for all vehicles. What if drivers could buy a transponder by Google using RFID technology and use it across all toll agency networks across the country?
While the experience would be much more seamless, it called into question the current structure of toll agencies and why they haven't joined forces already. I decided this was out of scope and focused on implementing a single feature improvement.