The Taxi Tracker

By Benjamin Shipman, Rishi Stevenson, Roisin

O’Dea

Background situation

• What is the background situation you are addressing? Describe the context users are experiencing.

Who? All persons over 18

What? Need to get around quickly

When? All the time

Where? London (UK version may be created)

Why? Because people take too long getting a taxi and knowing where they are

Problem

• What specific problem do people encounter in that situation? Use the results from your user research

The Taxi Tracker will help those who need to get around London quickly. So no more tardiness for meetings etc.

Question

• What core question are you addressing with the app?

The Taxi Tracker: How can you avoid taking so long to call one taxi that could be miles away. Hmmmmmmmmmm?

Key insight statement(s)

• Use your key insights statements from your findings during Scoping to provide evidence that your app is solving a genuine problem in a different way for users.

• The Taxi Tracker: Calling a taxi, wait for ages for it to eventually find you among the mass of crowds, or wait for a unoccupied one to eventually come your way… this isn’t a New York Movie. It doesn’t come exactly when you want it to as I’m sure any regular Taxi Traveller will know.

Mini Elevator Pitch

My team, [The Fluffeh Hyenas], are developing The Taxi Tracker,

to help People who wait ages for a Taxi that has that special

something (The layout and content) to help the disearning Taxi

Waiter.

User profiles

We found out that a lot of the people we interviewed were between the ages of 12 and 21, a lot of people also said that they would use this app because they think it is a smart way to commute. By seeing that we have a lot of young people that think its good shows this app can be suited to young people as well as adults and the elderly. A lot of people also said that the often have to look up the company and this will make a change to that.

Competitors or alternative solutions that already exist in the market

We haven't found an app that tracks a taxi although there are bus trackers, this can help us design our taxi app by looking at how they track the buses and what they use to calculate time.

MVP user stories and feature chosen

Our app mainly is good for seeing how far away your taxi is although it has other features we

believe that to see where your taxi is most important.

Flow of app

Key wireframes

Feasibility Data, content, technical

Data Feasibility • Does your app require data or content – Our app will require a Navigating

map. • Is the content owner happy to share it- We have not found out this

information yet so we will need to authorise this at a later stage. • Is there authorization required – We will need authorization from the black

cab taxi service to allow us to put a tracking/navigator device in the taxi. Technical Feasibility • Is your solution technically possible to build? – Yes our app is possible to

build. We know this because of other apps for example: Tfl bus arrivals , our app is fairly similar except it is for taxi’s.

• Could a professional developer build it in less than 3 months – Yes I think our app could be easily made in 3 months or less.

• Can you find a simpler solution, using existing technology- No I think our app is fairly simple already.

Business Case

• We have chosen to keep the app free as we think it will be more popular and

people would rather download a free app. • Overall most people said our app was between very good – to –good. No one

said this app was bad/very bad. People thought this app would be very useful for commuters.

• We have decided to keep this app free like other popular transport apps in the industry as we think a free transport app will be more popular and people would rather buy a free app rather than an app at an expense.

Marketing Strategy

• To get out Taxi Tracker app noticed we will advertise

it by:

• Social media eg: Facebook, Twitter

• Hand out flyers

• By mouth