I was contacted by a company aiming to streamline the car-parking process, by designing a dashboard for clients who use their product.
The client had recently rebranded their logo, aiming for a fresh and bright take on their company visuals - and wanted me to spearhead the next stage.
Another key consideration I kept in mind was maintaining a responsive design for the dashboard. This included editing my designs for use on mobile screens, to ensure that all functionality and legibility was maintained.
I think if I were to work on a project like this again in the future, I would take a bit of extra care in scaling down my designs in a consistent way instead of designing a 'mobile alternative' of the dashboard.
If I were to undertake a project like this again, I would do a number of things differently, aside from what I mentioned above.
In striving to maintain the colour consistency across designs, I think I may not have considered WCAG enough when it comes to legibility and accessibility.
Enabling in-depth statistics about recent use in full display on the dashboard may not be the best use of space - perhaps I could expand on payment information and confine these statistics to a separate page.
After my initial user research, I sketched out potential ideas for the dashboard design using the Crazy Eights method, and then went on to my low fidelity wireframes.
It was important that the user is able to access all important information and portals from the dashboard - this constricted me in having to fit a large amount of information in one screen without it looking too busy.
Fortunately I was also able to provide further information on payments on a separate screen.
