App Review

Before user feedback

Screen Shot 2017-05-25 at 11.55.56 am

After user feedback

Screen Shot 2017-05-25 at 11.56.18 am


App Review Sheet

Screen Shot 2017-05-25 at 11.51.49 amScreen Shot 2017-05-25 at 11.51.59 amScreen Shot 2017-05-25 at 11.52.09 amScreen Shot 2017-05-25 at 11.52.21 amScreen Shot 2017-05-25 at 11.52.33 am


Pitch – Workout App

You’ve decided to start working out where do you begin?

Workout is designed to let you create and follow your own workout routines. It keeps a record of workout data to help you see just how well you’re progressing. You can choose from a menu of exercises to put together a custom plan which you can follow at your own pace.

Week 7: App Interface Design (UI)

Launch screens

  • Launch screens are used to reinforce the branding of the app.
  • Also allows the app to load in the background.
  • Launch screens are not to be confused with the home screen, as you wouldn’t go back to the launch screen after getting into the app.

Examples of iOS launch screens:

Screen Shot 2017-05-25 at 10.06.21 am

Examples of Android launch screens:

Screen Shot 2017-05-25 at 10.07.38 am

The Tray

  • Allows the designer to add more space to the experience.
  • The tray can include navigation, tools, profile information.
  • The tray area should take up to 60-70% of the wide screen width.
  • It is important to be visible UI elements that make it clear that this element is clickable.

There are two main components to a tray:

  1. The active button
  2. The tray area

Screen Shot 2017-05-25 at 10.14.16 am

Some Rules for the tray

  • Make the shape unique.
  • Make the design look active.
  • Make a button look like it is part of the navigation.
  • Make sure it is large enough for a finger.
  • Make the button look different when it is touched.

Advanced Tray

  • A tray with a scrollable view can give access to a larger tray area.
  • Includes other UI Elements inside the tray.

Having most of the options and links in theThis can make the tray into the one stop area for accessing content.

Example of an advanced tray

Screen Shot 2017-05-25 at 10.20.28 am

Good Design: The Tray

  • Be clean and lean.
  • Keep the names short.
  • Don’t scroll much.
  • Don’t add other gestures.
  • Don’t overdo a good thing.

The List

  • The list is most commonly used in mobile user experience.
  • Opening second and third level pages.
  • Opening or expanding details for a content section.
  • Enlarging images.
  • Opening screen or options.

Example of a pattern using the list

Screen Shot 2017-05-25 at 10.28.50 am

Example of navigation buttons

Screen Shot 2017-05-25 at 10.32.02 am

Navigation buttons are used to return the user one space back in the experience.

Advanced List

Screen Shot 2017-05-25 at 10.33.43 am

There shouldn’t be any dead ends to a users exploration to ensure this we must make your last Page actionable.

To do this there are 2 methods:

  1. Provide an action button in the top navigation bar.
  2. Provide an action button below the page content.

Good Design: The List

  • Don’t overdo a good thing.
  • Don’t skip a step.
  • No dead ends.

This weeks lecture pod allowed me to have a better understanding on different UI elements. Having a better understanding on what should and shouldn’t be in different UI elements will aid in the development of my app. For my app I will most likely be using the List element.


Week 6: User Scenario

What is a User Scenario?

A scenario is a narrative describing foreseeable interactions of types of users and your product. Scenarios include information about a users goals, expectations, motivations, actions and reactions.

Scenarios are neither predictions nor forecasts, but rather attempts to reflect on or portray the way in which a system is used in the context of a daily activity.

User scenarios predict how certain types of users represented by your personas will interact with your product in a given situation in order to complete a give goal. User scenarios allow you to test your product structure before its fully developed and isolate problems before they become problems.

Scenarios should  at least outline the:

  • WHO

  • WHAT

  • WHEN


  • WHY

  • HOW of the usage.


User scenarios should be born from your user personas. you need to start with qualitative research so you can look for patterns in behaviours, goals among people how fit your user persona. out of this information you can better understand how a user may use your product and what goals they may have when using it.

As interactive designers it’s important to understand the process of using personas and user scenarios and a context to drive a design.

Week 5 & 6 lecture pods have showed me just how important it is to identify and understand the type of people you’re designing for. They have showed me that developing user personas and using them in scenarios is the best way to see how the product will be used. Scenarios can also be used to identify problems what you may have over looked. These two lectures have showed me just how important it is to create user personas and user scenarios during the development of my app.

Week 5: Personas

What are Personas and Artefact Personas?

User Personas

User personas are fictional users representative of a real user. User personas are a representation of the goals and behaviour of a hypothesised group of users. They are synthesised from data collected from interviews with users. That are captured in 1-2 pages descriptions include:

  • Behavioural Patterns
  • Goals
  • Skills
  • Attitudes
  • Environment or context, with a few fictional details to make them more realistic.

Here is an example of a user persona which should include the users:

  • Age
  • Sex
  • Occupation
  • Hobbies
  • Likes/Dislikes
  • other details germane to products.

The goal of defining these details is to establish the mindset and desires of the user. Personas are not only useful in the design process but also at the end to validate your wireframes to see if meeting your user’s goals.

Big Audience VS Little Audience

First we must establish who is your core audience and who is your fringe audience? Your design should satisfy your fringe audience but keep the focus on satisfying your core audience.

When defining personas we need to ask ourselves:


  • What are the tasks your user is trying to perform?

Are there different tasks for different personas?

  • Are there different tasks for different personas?

Different personas take different paths

  • What devices are your personas likely to use?

Are they expecting a cross platform experience?


Users who want to browse vs. users who want specific content.

Mental Models

Mental Models are what thoughts people from around an idea and activity. They vary from person to person.
2 examples mental models for taking a note:

  1. The young who would use a smartphone app
  2. The old who would use a post it

Mental models illustrate how your users approaches a particular problem.

Artefact Personas

As a way of thinking about the proposed official design of the product. They are useful for client meetings. To develop an artefact persona you’d ask product personality questions such as:

  • If the interface were a person, what would she or he be like?
  • How would you expect users to react when they first view the product?
  • How would you describe the product to a friend?
  • How is the product different from competitive products?
  • Which celebrity (or car, movie, etc) is the product more like or least like? why?

Also it’s important to choose experience keywords that would define and govern the visual strategy. experience keywords represent the initial 5 second emotional reaction that the archetypal persona should feel when viewing the interface.

This week’s lecture pod helped me understand just how important personas are when designing an app. It showed me just how much insight can be drawn from a simple user persona. It can help the designer see how the user may be thinking. This lecture will help be in creating my very own personas for my app

Week 4: Understand the Device

In order to really understand the smartphone you need to actually use the smartphone. Planning for an app on ios you should always practice using an iPhone and the same goes for android. This is because each platform has a set of unique elements, terminology, and device characteristics.

Part 1: Introduction to behaviours and gestures in IOS

The Tap
The tap is the building block of IOS platform. Usage of pressure sensitive glass enables the finger pressure of the user to come in contact with the screen. Minimum of 44 x 44 pt active area.

The Drag
The Drag uses the touch gesture to scroll walk. It combines push and the movement of finger to move an onscreen element.

The Flick
The flick is like the drag but flick allows for a lighter touch for quicker and less directed movement.

The Swipe
The swipe is based on using a large finger contact area for directed on screen movement. It’s meant for slower and more controller interaction.

The Pinch
The pinch allows for finger interaction to control zoom in and zoom out. Pinching inwards to zoom in and Pinch outwards to zoom out.

Random Gestures
There are lots of different gestures, for example, one of the most random gestures is the shake.

Part 2: UI – IOS Anatomy

Bars tell users where they are and helps users navigate or initiate actions.

Content Views
Content views contains app specific content and can enable behaviour such as scrolling, insertion, deletion and rearrangement of items.

Controls perform actions or display information.

Temporary views
Temporary views appear briefly to give users important information or additional choices and functionality.

The Keyboard
There are different keyboards for different tasks depending on the user’s needs, for example, text, email, phone or URL.

Pickers and Date Pickers
This element allows for larger contact area for touch gestures making it easier to pick selection options.

Inputs are app specific, the slider and the switch. These input methods can be used to create interactive message when selecting choice and images on the screen.

Tab Bar
The tab bar is one of Iphone’s signature navigation element for apps. It replaces tradition tabs found on most webpages with a language of icons small titles.

Navigation Bar
Native app navigation feature. The navigation bar plays a critical role using lists and pages in IOS.

The Tool Bar
The tool bar sits at the bottom of the screen and acts as a general placeholder for icons and text. The role of this element is to support the current view or page by providing secondary navigation.

The Action Menu
The action menu allows for secondary navigation within an app.

This should give a people a slightly better understanding of the anatomy of IOS. This lecture pod helped me to better understand the different elements that need to go into consideration when making an app. I now know that when developing my app I should keep some of these gestures and UI in mind.