Ironhack Prework: Challenge 1
Citymapper is an excellent alternative for frequent public transit users or those who opt for public transportation when traveling to new and unfamiliar places. It takes the guidance of Google Maps to a new level by offering more step by step instructions and details on price information and potential issues. The one feature this app seems to lack is the option to purchase tickets and I explored the possibilities of adding such a feature to the application.
I interviewed various frequent users of the New York subway system. These individuals use public transportation every single day to commute to work and tend to make use of public transportation options when traveling domestically or abroad. They use everything from the subway, ferries, trams, trains, buses, etc. The main issues they encounter when using these types of transportation include language barriers, lines to purchase tickets at kiosks, and the classic fear of looking like a tourist when wasting time trying to figure out a new system or kiosk. Interestingly, most of these individuals don’t seem to mind a physical ticket when it’s for their daily commute, but the annoyance stems from the need to carry around multiple tickets or stand in line for a one time ticket purchase. They also had a general concern with wifi and app malfunctions if that were to be the only way to access a ticket.
Of course, it’s difficult to solve all public transportation issues. I decided to create a ticket purchasing feature which focuses on the concerns with potential wifi and app malfunctions, as well as reduce the need to stand in line or carry around multiple physical tickets when doing extended transporting.
I’ve personally used the Apple Wallet application when I fly and have had great success with it. Most of my interviewees had also used Apple Wallet for the same purpose and found that to be a useful way to reliably use digital tickets — all purchased through different source applications. I wanted to provide the option to save all tickets purchased on the application to Apple Wallet so that the user feels secure that wifi won’t be an issue when using the tickets. I also focused on including instructions on how to use each ticket (scan ticket, present to an authorized individual, use this code to print — not all transit will be up to date — etc.) and making sure that finding your tickets is ALWAYS easy. Naturally, I also ensured that purchasing the tickets was a one button easy function that doesn’t change the experience of the app, but rather enhances it.
I learned a lot during this exercise about how to conduct useful interviews. A method I began to develop was starting with vague questions to learn about the individual’s general experience with the subject matter and then honing in on what priorities the individual has when they’re looking to use a product such as the one in question. I was able to think outside of my own concerns and priorities in order to implement useful features that I wouldn’t have considered on my own.
