May 19
Ironhack Prework: Citymapper & It’s Efficiency for the US_Challenge 1
Citymapper is a transit app meant to help people use real time information for public transportation. The app includes several options, such as Bus, Metro, Light Rail, Scooters, Ferry, walking, biking and more… These options are meant to map out time and show you how long it would take a user to get from point A to point B. The Citymapper app is inclusive of several large cities in the US and worldwide.
For the purpose of gathering information, interviews were held with a few candidates who live in the Bay Area (San Francisco / Oakland) and Los Angeles / San Diego. Each city has fully mapped transit options, but there are issues that interviewees raised with the efficiency of the app.
1. Understanding a Citymapper’s Concerns
The United States is a country predominantly founded on owning a car. Although in recent times, the use of electric scooters, further introduction of Electric Vehicles, metros and buses are becoming bigger and more important- personally owned cars still dwarf these transit options. The problem becomes how can a citymapper use the app without having personal vehicle concerns?
In the interviews with 5 locals of Los Angeles and San Francisco, CA, mixed issues were raised and benefits were talked about. The key points/concerns revolved around: 1. Lag time surrounding incoming transit options, predominantly buses due to personal vehicles causing traffic on the roads. 2. Interviewee’s enjoyed the already thorough app, but wanted more in terms of payment inclusivity. 3. This inclusivity and complete coverage of options is very helpful when looking for alternative transit options and route coverage once the selected option is taken. AND 4. ETA of transit while interviewee’s are en route.
2. Identifying and Defining Problems
Key problems are as followed:
Diving into these issues further. All four issues raise their own discussion, but for the purpose of this challenge, we will focus primarily on Problem #1… The lack of thorough, inclusive payment profiles to pay for all transport options.
3. Potential Solutions
While thinking of solutions that can help immediately, one idea arises: when you select your option for transportation, why not use a QR code? QR codes have proven to be easy to scan, adjustable based on what they are needed and conveniently available off the touch of a few buttons. Additionally, if an all-inclusive QR code is not available, having profiles that can be loaded for each system, transit options, is essential to pay and cover costs when in need of transportation.
4. Create a Prototype
Although the prototype looked at solving many of these solutions, the tope of the page shows what is current the next line under would be the implementation of a QR code. The following line shows a thorough ETA for traveling and intaking potential traffic and stops and lastly the end of travel notifications (CO2 saved, Calorie burned and money saved).
5. Testing & Feedback
Upon showing the steps to the interviewees, a similar conclusion was reached. An inclusive, central QR code would ease the need to pay and lessen the amount of cards, apps and other essential items to schedule and pay for transportation. Further details are needed for thorough implementation of a QR code on Citymapper as some cities in the US have too many transit options.
Post— What was learned
The US is not a small country, this challenge gave me the chance to converse and reach out to friends who I have not spoken with in some time. What was most enjoyable was the interview process where listening brought the interviewees/my friends relief and a chance to voice their concerns on a very serious topic in the US; transportation and infrastructure.
Prototyping these ideas were fun and a logistically creative way to present solutions. Although I find myself wanting more from this series of paper prototypes, it is a good beginning step to learn the process and give a chance to work on explanation skills when presenting.
