The MapSherpa Explorer mobile app was a brandable companion the the web based app.  It was designed to do what most of the web product did, and added GPS functionality that was lacking in the web app. The app became a bit of a utility knife as features were added to meet clients' needs. 

Below are a few early mockups that I created using AppCooker iPad app.  Branding was achieved later with Pixate, which was a kickstarter project I got pretty excited about.  It allowed you to create native apps, and then style them with a CSS like language that could be applied in realtime.

There were multiple views when tracking with the phone's GPS.  This screen shows dropping a marker and offers tools to attach a picture or populate details.  Appcooker

The compass view was cool looking, but overlaying on the map like this was instantly confusing to everyone.  One solution would be to rotate the map, but that technology hadn't arrived yet.  The developed solution made the background opaque.

The tracking view was a glorified stopwatch with geographic information displayed.  Later icons were added to help identify the metrics more quickly.  Again the overlay effect was scrapped and a better mechanism was used for the tabs. I can't tell which one is active can you?

When using a phone based GPS in the great outdoors, having cached maps is essential.  This UI allows users to select an area and download it to be used in the field.  This was part of the map buying part of the application which I've excluded from this collection of screens.  That concept was in the very early stages when these mockups were made.

This details screen demonstrates the pattern that was used for all information type screens.  The bar at the bottom was used as a toolbar instead of a tab bar.  As functionality was added it began to feel like a bundle of apps as opposed to a single app.  The secret to avoiding that is narrowing the focus of the app, which was a very active discussion when these screens were presented to the stakeholders.