Tips to make BMTC’s Android app more useful and helpful

BMTC has an Intelligent Transport System, and an ITS mobile application too. How to make this system more efficient to help public transport and people? some inputs.

In Bangalore, we see epic traffic jams on a daily basis. According the estimate in Revised Master Plan – 2031, Bengaluru’s economy suffered a loss of Rs 3700 crore in 2016 due to traffic jams alone!

The traffic jams can be reduced drastically if Bangalore Metropolitan Transport Corporation (BMTC) can attract people to ride buses, instead of using private vehicles.

So how can BMTC make the bus services irresistible to the public?

A passenger would gladly take the BMTC bus for his daily commute, if it meets the following conditions:

  1. It must cover the entire trip, door-to-door, with minimal walking
  2. It must be reliable and on time.
  3. It should be easy to find the latest and correct status of buses, on displays or mobiles.
  4. If one has to change buses, one doesn’t have to wait midway.
  5. One doesn’t have to stand in the bus. There must be assured seat, especially for journeys >10 minutes.
  6. The bus must directly head for the destination (no circular routes!)
  7. The trip must not be costly compared to private vehicles.
  8. It should be safe to ride at night (especially for women and children).
  9. The ride must be comfortable, with protection from heat and rain.

Well, if the BMTC smartphone app is well-designed, it can actually fulfill many of these needs, by making use of data from BMTC’s Intelligent Transport System.

However, the app suffers from multiple issues, and thus fails to attract new people to BMTC buses. These problems and their proposed solutions are listed below.

Problem-1: too many choices for commuter

The app offers a huge choice of stops and asks the user to choose a combination of stop and route. Then the app checks whether the stop-and-route combination is valid. If not, the user has to re-try.

This is an utter waste of time, for four main reasons:

  1. Most users do not know all stops by their name, and all routes by their codes, and which stop serves which routes. For example, most of the junctions like Marathahalli Bridge and Trinity circle have multiple stops, along all branching roads. Each stop serves a different set of routes. No user can be expected to remember all that information.
  2. Sometimes users may need to go to an unfamiliar area, where they may not know the bus stops and routes.
  3. The app shows the bus stops as a verbose list. Sometimes most of the names are similar to each other. Therefore it is very difficult to visualize which stop we are talking about.
  4. BMTC uses a large number of route variants (same route number, but different suffix letters). Most of these variants have only a small difference in their path. For example, all routes having “335” ply on the common path from Kundalahalli to KBS. If a user wants to travel within this common path, there is no point in showing buses of only one route variant at a time.

Proposed solution:

Assume that the user knows only the start and destination localities; but does not know anything about the bus stops or routes.
  • For the start point, the app should use the GPS, and show him all nearby stops on a map.
  • For the destination area, show all possible stops, on a map.
Let the user tap on one start and one destination spot. See the next topic for further logic.

Problem-2: importance on route numbers doesn’t help

The app does not address the real needs of a bus-passenger or a regular commuter:
  1. Most users are not particular about the bus stop or route number. Let the app find any bus going to the desired destination. Let the app choose the start and end bus stops; and also the route number. The only exception is circular routes, which are not preferred by users.
  2. Aged/invalid users may prefer to use only the nearest stop, as they cannot walk to stops faraway.
  3. If a user is in a rush, she may want to find the bus stop from where many more buses are available. Because, then the possibility of finding a convenient bus is more. Even if such a bus stop is farther away, he won’t mind the extra walking!
  4. On the outskirts, the user may want to find any stop where the next bus will appear in shortest possible time. Because in such areas, the overall bus frequency is very low. If one misses one bus; the next bus may arrive an hour later. Worse, if it is the last bus of the day, one could be stranded! So this feature gives one a better chance of catching a bus.
  5. Long-distance commuters want to find which of the incoming buses has free seats. For long journeys, traveling as standee is tiring. It is better to skip the next two buses if the third bus has free seats!
  6. The app must find an indirect combination route if there is no direct route. The passenger has to reach his destination, even by changing buses. She cannot give up where there is no direct bus. Therefore the app must cater to this need. just like Google Map).
  7. Flag the last bus for the chosen start and end bus stops; counting all routes. The passenger must get on board this bus at any cost, to avoid being stranded.

Proposed solution:

Provide these options. Note that some of these solutions must process the bus schedule, rather than the GPS locations of buses that are already on road. For example,
(a) calculating the bus frequency counting all routes between two stops,
(b) flagging the last bus, etc.

Problem-3: no option to save a particular search

Often a daily commuter wants to check the bus status on his fixed route (home ↔workplace). Currently this can’t be saved in the ITS app.

Proposed solution:

Let users save their queries, favourite them and make it easy for them to search for it next time. The result can also be shown immediately in a separate pane.

Problem-4: confusions

The app asks the user to enter the start and destination stops, but then again takes a back-step and asks more questions about the start stop. This is confusing.

Proposed solution:

Finish the identification of the start stop first, and then proceed to the destination stop. (Note: If the app stops asking the user to specify particular stops, then ignore this comment.)

Problem-5: time-consuming procedure

The app relies on verbose questions. This is confusing, and time-consuming.

Proposed solution:

Just show a map, with markers and route lines. Let the user select.


The app cannot work on Wi-Fi connection. This makes it very costly to run. Many users would check up the bus from their office/home, where the Wi-Fi data is mostly free (or at least, much cheaper compared to mobile data).

Proposed solution:

The app should prefer WiFi data connection (if available).

Problem-7: unnecessary downloads

The app downloads a lot of data even before ascertaining what the user needs.
This gives rise to two problems:
1. The start up time becomes too long
2. The data consumption is too high.

Proposed solution:

It should wait to see what the user needs and then pull data only as needed. This will eliminate the start-up time, and won’t be costly to operate.

Problem-8: lack of realtime road usability data

The app does not display any roadblocks along the routes (compare with Waze app).

I have often faced this issue: Often some major road work blocks a road, and the buses are diverted for a few days. As a result, some stops are not served for a few days. But this information is not reflected in the app.

Proposed solution:

Mark such places on the map, and block that stretch of the road. Show the diverted route till it is in effect.

With these improvements, I think the BMTC ITS app would be much more useful than it is now, for a lot more people, and will help improve the footfalls in the buses.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Similar Story

Lok Sabha elections 2024: North East Delhi — Know your constituency and candidates

In the high profile contest for North East Delhi, BJP's star MP Manoj Tiwari takes on the firebrand Kanhaiya Kumar (INC). Who are the others?

Table of contentsAbout the constituencyAt a glanceMap of the constituencyFind your polling boothPast election resultsIncumbent MP : Manoj Kumar TiwariOnline presenceCriminal casesPositions heldAssets and LiabilitiesPerformance in ParliamentMPLAD funds utilisationCandidates contesting in 2024Key candidates in the newsIssues of the constituencyAlso read About the constituency Well known for its high migrant labour population from the states of Haryana, Uttar Pradesh and Bihar, North East Delhi constituency comprises the following areas: Burari, Timarpur, Karawal Nagar, Ghonda, Babarpur, Gokalpur (SC), Seemapuri (SC), Seelampur, Rohtas Nagar and Mustafabad. This constituency has the highest average population density of 36,155 persons per square km — the highest…

Similar Story

Lok Sabha elections 2024: Chandni Chowk — Know your constituency and candidates

Delhi-based businessman, Praveen Khandelwal of the BJP takes on Congress' Jai Prakash Agarwal. Know more about them and other contenders.

Table of contentsAbout the constituencyMap of the Constituency Find your polling boothIncumbent MP: Harsh Vardhan, BJPOnline PresenceCriminal CasesPositions HeldPerformance in ParliamentMPLAD fundsCandidates contesting in 2024Key Candidates in the newsIssues of the constituencyAlso read About the constituency  Chandni Chowk Lok Sabha constituency is one of the seven Lok Sabha constituencies in the Indian National Capital Territory of Delhi. This constituency came into existence in 1956. It is the smallest constituency of Lok Sabha in terms of area. Since the delimitation of parliamentary constituencies in 2008, it is made up of ten assembly constituencies, which are Adarsh Nagar, Shalimar Bagh, Shakur Basti, Tri…