CoPilot Truck, installed on iPad 9.7, my experiences

Garmin has a nice Up Ahead feature for truck stops, WalMarts, etc. Garmin is a full featured unit, but the routing is atrocious. I gave up on my Dezl 770 after two years of use.

The Garmin maps are lacking in detail, can’t zoom in, or out, so it’s difficult to see the flakey route given, or how to compensate for the route.

After two years of “WTF IS THIS THING DOING?”, I gave up.

 

Since the coding and maintenance teams are most likely broken into geographic regions, I’m not surprised if one region is rendered more accurately, and another region is rendered so poorly that users in that area abandon use of the device.

Which may simply be one team leader winning more resources, while another is at odds with the manager deciding allocation of resources.

The silliness, to me, as I use these devices, is the “low-hanging fruit” of usability that should come with generic software toolboxes.

For example, we understand a five stop “milk run” as a list of stops, but a beginning and end is a list also.

Any programming language will have list management functions, or the ability to accept a library of those functions. The most versatile structure being a doubly-linked list, to allow swapping destination with origin, for example, for the return run. Google and Mapquest offer it, but not CoPilot. What is the caliber of programmers being attracted to navigation software?

 

The Favorite names can be 55 characters.

 

String-handling functions are clumsy, and not typical.
You either accept the proposed Favorite name as-is, or start over. Not possible to prefix or suffix the proposed name; it vanishes with any keystroke.

Typical IOS edit functions are disabled.

 

When you get this far, tap the Map button.

 

And you then see up to three route options.

Tap the option you want.

 

If you tap the Calculate button...