<aside> 👋
This, and all of the blogs, give an overview of the process and steps taken for each part. I’ve included images taken from the Figma File where the majority of the work lives to illustrate the process.
If you would still like to see further details on each part, please view the Figma File in full.
It can be found at the end of this page, or on this master page.
</aside>
V4 should be the final version of the Metronet before hand in, and mainly be made up incremental tweaks from user feedback.
An issue I found from testing was that users wanted different ways to view routes when planning. Originally, I had focussed on tailoring each view depending on the situation, for example if they were trying to go somewhere immediately, the routes would take up more room on the screen as the user is less likely to need options in that scenario. I think this was good idea, but it seems users want more choices.
To rectify this, I came up with the idea of a slider letting users change between an expanded, condensed, and map view of the routes they were choosing. I felt this worked well and didn’t interrupt the experience.
I found in testing users wanted a shorter onboarding, so I wanted to see what I could trim. One area I was able to cut down was the account creation, by removing passwords. This is an trend more brands are using as 2FA is basically a standard now anyway. I had also considered social sign-in, but I don’t necessarily agree with as a concept as it centralises everything so it’s easier to loose access to all your accounts.
Users in testing appreciated the moments of guidance throughout the app, so I thought about adding more guidance in the navigation flow. I had an idea that would offer users quick guides to certain ticketing systems or services in a few sentences. This was optional and mainly useful for novice or visiting users, but felt it was a really strong idea. The first one I tried was for the Glider ticketing system, as getting on without a ticket is a problem I see lots of first time passengers get into. I want to push this further and think about what other issues could be solved with these little bits of guidance.
One thing came up from feedback was wether “tickets and passes” and “upcoming journeys” should actually be combined as they shared similar contents. After some experimenting I think it would be overwhelming to have them combined, so instead I’m focussing on adding in moments of cross promotion between the two, such as if you’re looking at an upcoming journey it offers you to view the tickets and vice versa.