All work / Case study 02

About 5 minutes to read

NaviBus A local bus tracking app

A concept app for finding bus timings, tracking a bus live and saving the routes you take often. I shaped it around a survey of 38 regular bus users.

Full case study on Behance

Role
Designer: survey, competitor review, user flows, paper wireframes, UI
Project
Concept app
Period
Published June 2025
Status
Concept, not built
Tools
Figma, ProtoPie
Splash screen: the NaviBus logo, a bus drawn around the letters NB, on a teal background with the line Fast. Simple. On time.
Home screen: Welcome to NaviBus, From and To fields with a Search Buses button, a Recent Search list (Museum Road, BMS Hospital) and Favorites (College Bus Stop, New Market), with a tab bar for Home, Tracker, Complaint and Profile.
Home screen dimmed, with a Select Language menu open at the top right: English (default), Malayalam, Hindi and Tamil.
Fig. 01Splash, home and the language menu. Search, recent routes and favourites share one screen, and the language switch sits in the home header. Scroll sideways to see all three screens.
01

The problem

People who take local buses deal with timings that are wrong or out of date, apps that are hard to follow, and no way to keep the routes they use every day. Most bus apps either show too much or show timings you cannot trust.

I saw room for a simple app focused on clarity and real-time accuracy.

Status

A concept project, not a built app. This page shows research and design reasoning, not results.

02

What 38 bus users told me

Before designing anything, I surveyed 38 regular bus users about how they travel, what goes wrong and what they would want from an app. They could pick more than one answer.

were aged 18 to 25
63.2%
named overcrowding as a problem (32 of 38)
84.2%
wanted live bus tracking (30 of 38)
78.9%
rated themselves 4 or 5 out of 5 likely to use a bus app
29 of 38

Problems with local bus services

People who chose each, out of 38

  1. Overcrowding32 · 84.2%
  2. Inadequate information13 · 34.2%
  3. Unsafe travel11 · 28.9%
  4. Irregular timings9 · 23.7%
  5. Lack of cleanliness9 · 23.7%
  6. Poor staff behaviour9 · 23.7%
  7. Payment issues6 · 15.8%
  8. Sometimes no bus available1 · 2.6%
Fig. 02Overcrowding was named far more often than anything else.

Features wanted in a local bus app

People who chose each, out of 38

  1. Live bus tracking30 · 78.9%
  2. Timetable or schedule view25 · 65.8%
  3. Seat availability24 · 63.2%
  4. Online ticket booking21 · 55.3%
  5. Notifications and alerts20 · 52.6%
  6. Fare calculator20 · 52.6%
  7. Customer support chat19 · 50%
  8. Route planner18 · 47.4%
Fig. 03Live tracking was the most wanted feature.

How often they take the bus

Share of 38 respondents, one answer each

  1. 23.7%Daily
  2. 18.4%A few times a week
  3. 36.8%Occasionally
  4. 21.1%Rarely
Fig. 04Fewer than a quarter ride every day.

Overcrowding was the top problem by a wide margin, and this first version of NaviBus does not solve it. That is why crowd detection is first on my list of what comes next. Live tracking, the feature most people asked for, is the first of the three stories below.

03

Three apps compared

I compared what I planned for NaviBus with redBus, a second bus app and Google Maps. None of them let you switch language. Only Google Maps had live tracking and saved routes.

Features of NaviBus compared with three existing apps
FeatureNaviBusredBusSecond bus appGoogle Maps
Real-time bus trackingYesNoNoYes
Easy accessibilityYesYesYesNo
Complaint registrationYesPartlyPartlyYes
Language switchYesNoNoNo
Favourite routesYesNoNoYes

YesPartly: there, but not easy to useNo

04

Four tabs, sketched on paper first

The app has four tabs: Home, Tracker, Complaint and Profile. Home is for searching and for the routes you already use. Each of the others does one job. I sketched every screen on paper before moving to Figma.

  1. Start app
    1. Home
      • Home
        • Recent searches
        • Favourites
      • Tracker
        • Search bus
          • By stop
          • By bus no.
          • By route
      • Complaint
        • Private
        • Public

        Confirmation, after either kind of complaint

      • Profile
        • Sign in
Fig. 05User flow, redrawn from my original diagram. Both kinds of complaint end on the same confirmation. The diagram calls the first kind Private; the final screens call it Personal.
Pencil sketches on lined paper: a tab bar for Home, Tracker, Complaint and Profile, then sketches of the home screen with a language button, the tracker with a Waiting to search card, the complaint chooser with Personal and Public, the profile menu, search with By Bus, Route and Stop options, bus results with Edit and Filter, and the complaint form. A note at the right edge, cut off in the photo, reads: to file a complaint, user needs to login.
Fig. 06Paper wireframes. A note on the sheet set one rule early: you sign in before filing a complaint. Scroll sideways to see the whole sheet.
05 · Feedback 1

Real-time tracking and accurate times

A local bus app should offer real-time tracking, reliable updates, easy navigation, and secure, user-friendly features to build trust and ensure regular use.

Survey respondent

Each search result names the operator and the bus’s current stop, and most also show the minutes until it arrives and the arrival time. Track Bus opens a live map with the route, the current stop, the next stop and the time left. Before you choose a route, the tracker tells you what to do instead of showing an empty map.

Search results from Town Bus stand to Museum, with By Stop, By Bus No. and By Route options and filter chips for All, A/C, Private and KSRTC. Cards for Bus 53, 58 and 63 show the operator, current stop, minutes until arrival and the arrival time; Bus 87 shows only its operator and current stop.
Track your Bus: a map with the bus route drawn in teal and a card below: Destination Museum, Bus 58, Time 10 mins with a refresh button, Current Stop Indoor Stadium, Next Stop Premetric Hostel.
Tracker before a route is chosen: a map with a search bar and a card that reads Waiting to roll? Search for a route to start tracking your bus.
Fig. 07Results with arrival times, live tracking, and the tracker’s empty state. Scroll sideways to see all three screens.
06 · Feedback 2

Clear categories, and a way to complain

Local buses, city buses and KSRTC buses should be classified differently according to their route so that people can easily access it. There should be a complaint registering setup and it should be monitored and rectified.

Survey respondent

Results filter by All, A/C, Private and KSRTC, and every card names its operator (Fig. 07). Complaints come in two kinds. A personal issue, like a missed bus or an overcharged fare, is handled privately. A public issue, like a broken bus stop, affects every passenger. Both end with a complaint ID.

Choose How to Report: two large cards. Personal Issue: raise a concern specific to your own experience. Public Issue: report a problem affecting multiple passengers.
Report a Personal Issue form: this complaint will be treated privately. Fields for bus number, route, date and time, issue type (Missed Bus, Fare Overcharged, Driver Behaviour, Other), a description and an optional photo upload.
Complaint Submitted: a teal tick, a thank-you message, Complaint ID #NB4523 and the date, with Return to Home and Submit another complaint.
Fig. 08Choose a type, fill in the details, get a complaint ID. Scroll sideways to see all three screens.
07 · Feedback 3

Easy to get around

Easy accessibility.

Survey respondent

Search works three ways, by stop, by bus number or by route, so you can start from whatever you know. Searching by bus number needs only one field. Recent searches sit right under the form.

Search with By Stop selected: Search for Source and Search for Destination fields, a Search Buses button and recent searches shown as from-to pairs.
Search with By Bus No. selected: a single search field, a Search Buses button and recent searches.
Search with By Route selected: source and destination fields, a Search Buses button and recent searches.
Fig. 09By stop, by bus number, by route. The form changes to ask only what each search needs. Scroll sideways to see all three screens.
08

Type and colour

Inter for headings and buttons, Instrument Sans for body text and key labels. Teal is the primary colour and violet the secondary, on white and light grey.

Type specimens from my style sheet: Inter, for headings and buttons, and Instrument Sans, for body text and key labels, each shown as NAVIBUS and navibus in three weights.
Fig. 10The two typefaces, cropped from my style sheet.
  • Primary#00B4BC
  • Secondary#5B5FCD
  • Surfaces#FFFFFF
  • Backgrounds#F8F8F8
  • Text#000000
  • Text#212121
  • Text#564F4F
  • Inactive#9E9E9E
Fig. 11Two brand colours and six neutrals, redrawn from my style sheet.
09

What comes next, and what I learned

This version covers search, tracking, saved routes and complaints. Four features I would add next, starting with the problem people raised most:

  1. Crowd detection. Estimate how full a bus is in real time, so people can choose a less crowded one.
  2. Better route suggestions. The fastest or most reliable route for the time of day, traffic and schedule.
  3. Seat booking. Reserve a seat in advance on certain routes.
  4. Fare alerts. Fare changes, discounts and best-value routes.

What I learned

Clarity and consistency matter most in tools people rely on every day. Small details, like saving a frequent route or taking a step out of search, have a real effect on how usable an app is. Good design is not just clean visuals. It is reducing friction, solving actual problems and anticipating what people need.