We’ve all been there... standing at the crowded baggage belt & impatiently wondering why our bags are taking so long to arrive. This proposal is an attempt to take the stress out of getting our bags from the belts, safe and sound without getting anxious in large crowds & waiting unnecessarily.
Image source: smartertravel.com
Here, we identify some early parameters to work with:
Let's map this out visually to reveal the nuances of the entire experience of the user collecting their baggage.
This notification is critical to alerting the user about their baggage information and is giving them a clear call to action of Tap to Track.
Tapping the notification takes them to this screen where they can see:
Once the user taps on a particual bag, they can see the exact journey path that it has taken in the entire journey till now.
The track my bags screen is what the user will keep scanning time to time so we have to ensure that we keep updating the status to inform them about the ETA of their bags in case they are stuck at immigration or want to shop at the airport.
Once we know that the bags are on the carousel, we can intelligently suggest them to book a cab right from the status screen.
Things often do not go as we expect them to so we must also be prepared to handle circumstantial scenarios like baggage being misplaced or status not visible. What do we do then?
In a scenario where upon landing on Track my bags, baggage status can't be fetched we can provide functionality to manually add baggage or contact the airline staff.
Tags can be scanned by a camera and upon successful scanning we can get baggage details thereafter.
A support chat bot could help resolve user queries as user might not have an active mobile network or credits to make a call. As an addition, we can provide a voice call functionality as well.
This mock is a representation of how the information architecture cohesively comes across as a single unit to serve the needs of the user in accordance of:
An exploration in motion of the baggage path, the ETA and the final notification of arrival along with serving the call to action for booking an Uber
This proposal is one way of tackling how we can help the user to track their baggage and I also understand that it is proposed under certain assumptions that are:
This exercise was done in a total of 450 minutes distributed as follows:
Scenario extrapolation (50 mins) + Mapping the sequence (75 mins) + Sketching & Wireframing (150 mins) + High Fidelity Representation & Motion Exploration (175 mins)