Paper Prototype | Process Blog

Paper Prototypes

Logging in

We chose this idea as our first primary task because we want each user to have their own profile. They will have the ability to create their own profile so they can access route saving, as well as payment management.

In this paper prototype, the user first opens the Eazy Transit app and is prompted to log-in to be directed to the home page.
A strength of this prototype is that this log-in process follows standard platform and industry conventions, and while it is not something evolutionary, it offers the user an opportunity to create an identity within the app by creating a profile to use for Eazy Transit.
A weakness would be that the user is prompted to sign-in or sign-up to enter into the app, and some users may turn away from this request.
Some originality shines in this prototype with the Eazy Transit logo maintaining present throughout each step while logging in, and this process is feasible for users because they are most likely used to the familiar concept of logging into a system to access its features.

Planning your trip

As a transportation application, one of our primary features is trip planning. It has all the features of google map to search for a destination and travel there instantly.

This prototype shows the happy path of how a user would utilize trip planning in our app.
A strength of this is its simple functionality (we included the search bar at the bottom so it is easy to use). The user needs to tap “Search”, enter their destination (with suggestions), and tap the route they desire to begin navigation. In total, 3 non-keyboard button taps.
A weakness of this potentially is that historically, search functionality has been at the top of the page, so it may take some adjustment with us having moved it to the bottom. However, we believe this will lead to a more convenient experience

Viewing saved routes

Since our user will likely be going to the same destination repeatedly, the saved routes page will be a page that they can quickly select their route without searching for a route repeatedly.

This prototype shows the interaction of viewing the routes and trips the user has saved.

The strength of this design is the ability to swipe across the saved trips and routes and quickly pick the route the user needs without having to go through several pages to find the route they want. On the route options page the user can see what bus stop they have saved for that particular route. The options to change the bus stop (pick up point, time schedule, full route options are quickly accessible.
One of the problems with this prototype is on the route options page, the options here might have some frequency of use problems. The “see full route” or “see time schedule” buttons may be used more frequently than the “change pick up point”. Another problem is the placement of the remove route button, users may accidentally press remove route when they are trying to tap on “see full route” or the “start trip” buttons.

Adding payment options

As an application that is used for transportation, it is also important to add payment information to the application for user convenience. We also provide a variety of payment options.

We consider this one of our strengths because this process is similar to what the user is used to. We believe that the user would find this feature very convenient.

One weakness would be the typing keyboard would sometimes cover the name on card making it hard to see what you are typing. This could be easily fixed to make the screen scroll up.
It is feasible because the design is simple and it is similar to other applications.
As of originality, not many payments can include ORCA card. So for the users that already use ORCA cards, they can simply add their ORCA cards to this app.

A secondary task is to view the past payments. You can find what trips, transportation you take and how much money spent.

The strengths of the past payments design is that we can see information of each trip. The description or title of the trip, the transportation methods used in the trip, and the total amount of the trip giving the user a clear idea of the payments.
The weakness would be visibility. You would have to make the space between each information ideal so that the users will not have a hard time finding the information they want.
It’s pretty feasible since the lists could be created my mapping the information from the database. The design is also pretty simple.

As of originality, we believe that although it may have visibility issues, with the correct design, we can show important information. The icons of the transportation method is also what makes this design special.

Editing your profile

Creating an account is essential to storing the routing, payment information.

In this paper prototype, the first image starts once the user has clicked on the ‘Account’ icon in the bottom right corner of the screen.
A strength here is that the interface exhibits qualities of empathy, in the way that it first greets the user with “Hello, ___.”
A weakness surrounding this feature is the notion of how motivated the user would be to fill out their information (e.g. taking the time to add a profile photo)
This is a feasible feature and is cohesive with some other common Account settings features on other apps. However, in terms of originality, it is not largely original.

Paper Prototypes

Logging in

In this paper prototype, the user first opens the Eazy Transit app and is prompted to log-in to be directed to the home page.

A strength of this prototype is that this log-in process follows standard platform and industry conventions, and while it is not something evolutionary, it offers the user an opportunity to create an identity within the app by creating a profile to use for Eazy Transit.

A weakness would be that the user is prompted to sign-in or sign-up to enter into the app, and some users may turn away from this request.

Some originality shines in this prototype with the Eazy Transit logo maintaining present throughout each step while logging in, and this process is feasible for users because they are most likely used to the familiar concept of logging into a system to access its features.

Planning your trip

This prototype shows the happy path of how a user would utilize trip planning in our app.

A strength of this is its simple functionality (we included the search bar at the bottom so it is easy to use). The user needs to tap “Search”, enter their destination (with suggestions), and tap the route they desire to begin navigation. In total, 3 non-keyboard button taps.

A weakness of this potentially is that historically, search functionality has been at the top of the page, so it may take some adjustment with us having moved it to the bottom. However, we believe this will lead to a more convenient experience

Viewing saved routes

This prototype shows the interaction of viewing the routes and trips the user has saved.

Adding payment options

We consider this one of our strengths because this process is similar to what the user is used to. We believe that the user would find this feature very convenient.

One weakness would be the typing keyboard would sometimes cover the name on card making it hard to see what you are typing. This could be easily fixed to make the screen scroll up.

It is feasible because the design is simple and it is similar to other applications.

As of originality, not many payments can include ORCA card. So for the users that already use ORCA cards, they can simply add their ORCA cards to this app.

The strengths of the past payments design is that we can see information of each trip. The description or title of the trip, the transportation methods used in the trip, and the total amount of the trip giving the user a clear idea of the payments.

The weakness would be visibility. You would have to make the space between each information ideal so that the users will not have a hard time finding the information they want.

It’s pretty feasible since the lists could be created my mapping the information from the database. The design is also pretty simple.

As of originality, we believe that although it may have visibility issues, with the correct design, we can show important information. The icons of the transportation method is also what makes this design special.

Editing your profile

In this paper prototype, the first image starts once the user has clicked on the ‘Account’ icon in the bottom right corner of the screen.

A strength here is that the interface exhibits qualities of empathy, in the way that it first greets the user with “Hello, ___.”

A weakness surrounding this feature is the notion of how motivated the user would be to fill out their information (e.g. taking the time to add a profile photo)

This is a feasible feature and is cohesive with some other common Account settings features on other apps. However, in terms of originality, it is not largely original.