Mobile App Prototype for EDIT – Almudena Clementine

Context

This project was the result of a workshop at EDIT. My team and I had to work on an app for the academy. The goal was to implement a lean methodology. We had limited time, so we spent less time researching. This was conceivable since we, as students, were among the target users.

Context

Opportunity

To design an app that allows individuals to interact with the school.

EDIT is an academy that focuses on digital and interactive design, creativity, technological and mobile development, and digital marketing. The academy just had a webpage when the workshop took place.

The challenge was developing an MVP to validate our assumptions and conclude the workshop with a solution. We ended up focusing on only one user flow due to the workshop’s time constraints.

Opportunity

To design an app that allows individuals to interact with the school.

The challenge was developing an MVP to validate our assumptions and conclude the workshop with a solution. We ended up focusing on only one user flow due to the workshop’s time constraints.

App

We maintained the client’s visual identity. Here are some mock-up screens from the final design.

Prototype in Axure

Research

Instead of interviewing the stakeholders (EDIT) and the target users (students currently enrolled and potential students interested in a digital training), we worked based on our own assumptions. A competitor analysis was also omitted due to time constraints.

Example of our assumptions in important features:

Application form.
Personal area for students:
- Access to the recommended a bibliography and other content shared by the teacher.
- History of all the courses attended. Recommendations for future courses.
Chat for contact (chat bot when the school is closed).
Calendar with events.

Problem Statement

The app was intended to:

Produce an increase in the number of applications.
Present the available courses in an appealing way.
Increase the awareness of the school in the market.

We identified what the website wasn’t offering:

A simple application process.
It had many visits but not many applications.

Overall it didn’t make the school a top of mind brand for courses in this area which was causing loss of potential customers.

We set ourselves to measure the success of the app through:

The number of downloads.
The number of applications made through the app.
The % of contacts made through the app per month

Research

Example of our assumptions in important features:

Application form.
Personal area for students:
- Access to the recommended a bibliography and other content shared by the teacher.
- History of all the courses attended. Recommendations for future courses.
Chat for contact (chat bot when the school is closed).
Calendar with events.

Problem Statement

The app was intended to:

Produce an increase in the number of applications.
Present the available courses in an appealing way.
Increase the awareness of the school in the market.

We identified what the website wasn’t offering:

A simple application process.
It had many visits but not many applications.

Overall it didn’t make the school a top of mind brand for courses in this area which was causing loss of potential customers.

We set ourselves to measure the success of the app through:

The number of downloads.
The number of applications made through the app.
The % of contacts made through the app per month

Personas

We created 2 personas based on our own insights and experience:

Professional profile: someone in their 30s who wants to gain a new skill or switch careers.
Recently graduated student profile: someone in their 20s who is looking for a specialization, and who may welcome some career choice advice.

Design / Prototyping & Usability Testing

We worked mainly on using ‘gamification’ to humanize the course selection and the application flow.

The Persona we chose to focus on was the recently graduated student (‘Maria’) who is feeling a bit lost and indecisive and is looking for some guidance on choosing the right course.

We went on to produce a Low-Fi paper prototype. After that, we tested it with possible users using Pop Marvel.

The feedback we got from our first test was the following:

The flow was light and fast.
The language used was pleasant and turns the process into a conversation.
The first screen (‘do you know what you want: yes/no’) was regarded as confusing, and needed better copywriting.
The circles didn’t match the visual identity of the brand, which are squares.

We used this feedback to improve our flow and wireframes.
We then tested the prototype before moving to the UI phase.