PROJECT PART 3 : CONCEPTUAL & PHYSICAL DESIGN

Task 1 : Interaction Metaphor

Interaction Metaphor: Driver's Point of View

When designing UTM Drive, we didn’t want drivers to feel like they are learning a “new system.” Most UTM drivers are students who drive part-time and usually accept rides in between classes or during peak hours. So the main idea was to make everything feel familiar, like things they already use every day. Instead of complicated UI ideas, we used simple real-life metaphors so drivers can instantly understand what’s going on without thinking too much.

1. Ride Requests = “Job Inbox”

Think of ride requests like a job inbox.

Instead of scrolling through a noisy Telegram group, drivers open the app and see a clean list of ride requests just like checking emails or delivery orders. Each request is shown as a card with pickup, drop-off, fare, and time.

So the driver’s mindset becomes:

“Okay, these are my available jobs right now.”

Justification:

• No more missed messages.
• Requests don’t disappear.
• Easy to scan and choose quickly.

2. Accept Button = “Handshake”

When a driver taps Accept, it’s basically a digital handshake. Once you accept, both the driver and passenger know the ride is confirmed. No more “bro are you coming?” messages.Everyone understands what a handshake means agreement.

Justification:

• No confusion.
• No double booking.
• Feels official and secure.

3. Ride Notification = “Buzzer”

New ride request notifications work like a doorbell/buzzer.

Just like how a doorbell tells you someone is at your door, the app tells the driver:

“Hey, someone needs a ride now.”This is super useful because drivers are often doing other things driving, waiting, or resting.

Justification:

• Important requests don’t get ignored.
• No need to keep opening the app.
• Clear sound/vibration = instant awareness.

4. Map = “Campus Guide”

The map in UTM Drive works like a campus guide, not a complicated GPS.

Instead of random coordinates, drivers see familiar places like:

• Kolej Tun Razak
• FKE
• Library
• Common pickup spots

Drivers already know these places, so the map feels natural.

Justification:

• Less confusion during pickup.
• Faster navigation.
• Easier for new drivers.

5. Ride Status = “Itinerary”

Every ride is shown like an Itinerary:

• Request received
• Ride accepted
• Arrived at pickup
• Passenger onboard
• Drop-off completedDriving itself is a journey, so this just makes sense.

Justification:

• Always know what stage they’re in.
• No guessing what to do next.
• Makes the trip feel structured.

6. Fare Display = “Receipt”

Before accepting a ride, the fare looks like an invoice/receipt.It clearly shows the price, so drivers don’t have to negotiate or worry about surprises later.

Justification:

• Feels fair and transparent.
• Builds trust in the system.
• No awkward money conversations.

Why might these Metaphors work well together?

All these metaphors come from things drivers already know:

• Inbox → job list
• Handshake → confirmation
• Buzzzer → alert
• Campus guide → navigation
• Journey timeline → trip progress
• Receipt → payment
• So drivers don’t feel lost or confused. Everything feels logical and connected. Overall, these
• metaphors turn UTM Drive into something that feels organized, predictable, and stress-free,
• especially compared to the messy Telegram group system.

Interaction Metaphors :Passenger’s Point of View

In UTM Drive, interaction metaphors are carefully selected to help passengers understand and use the system intuitively while supporting safety, efficiency,and trust. By mapping digital interactions to familiar real-world experiences, the system reduces cognitive effort and improves user confidence, especially when

compared to the previous unstructured Telegram-based approach. From the passenger’s perspective several interaction metaphors are particularly suitable.

1. Ride Booking = “Ordering a Ride”

Booking a ride in UTM Drive is like ordering a ride through a familiar e-hailing app. Passengers only need to enter their pickup and destination, and the system handles the rest.

Justification:

• Reduces complexity, saves time, and eliminates the uncertainty of manual booking through Telegram.

2. Ride Confirmation = “Booking Confirmation”

Once a driver accepts the ride, passengers receive a clear confirmation, similar to a booking receipt or confirmation message.

Justification:

• Provides reassurance, reduces anxiety, and builds trust in the system.

3. Driver Tracking = “Waiting for Delivery”

Passengers can track the driver’s location in real time, similar to tracking a food delivery.

Justification:

• Reduces waiting stress and improves time management at pickup points.

4. Fare Display = “Price Tag”

The fare is shown before booking, just like a price tag in a store.

Justification:

• Ensures transparent pricing and avoids misunderstandings or negotiation.

Task 2: Storyboard hand sketching:

Story Board 1: Student POV

Story Board 2: Driver's POV

Task 3 :WireFrame Sketching

WireFrame Student POV :

WireFrame Driver POV :

Concept Video:

youtube link : https://youtu.be/JvdKf6sQ7iM