Liftango

In order for me to be able to build upon the apps as they existed I had to consolidate all the various pieces of design that had been commissioned prior to my involvement. By doing so I quickly realised that there were three states of the apps that need to exist from a design point-of-view...

'Release'
This was the state of the app that perfectly matched the live app that was available for download.

'Playground'
A state of the design that included all features regardless of whether they were in development yet or not. It was a version of the app that existed as a future version where all features had been built and implemented.

'Development'
The state of the app that closely matched the live version but with the features the development teams were currently building. This design sat right in the middle between the live 'Release' state and the'Playground' state.
‍
The reason the 'Playground' and 'Development' designs could not be the same was because often features were being further designed and integrated with other features before they had been built and released. For the sake of clarity between what the developers were working on and what features had been approved there needed to be two separate designs.

Then with a design of the live app and an already growing list of clients who had their own white-label versions, whether it was On-Demand Carpool or On-Demand Public Transport, I worked with the Sales team to create a system where they could show potential clients what their own branded app would look like. Leveraging the power of symbols in Sketch, like a design system, all that was required was three of their branding colour (primary, secondary and accent), their logo and a location for the map component. With those elements, I could quickly create a ready-to-go design that could be included in sales pitches and proposals. The plan was to turn this into a tool that removed the Designer and potentially lived on the Liftango website for prospects to use themselves.