Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

Charitable Connections

Section
borderfalse
Column
width20%

Group Members

  • Emily Kuo (ekuo8)
  • Gil O'Neil (goneil)
  • Max Stein-Golenbock (msteing)

GR1 - User Observation and Analysis

GR2 - Designs

GR3 - Paper Prototyping

GR4 - Computer Prototype

GR5 - Implementation

GR6 - User Testing

Column
width80%

Client Design 2

Description

In our second design we had illiterate users on our minds. Although we couldn’t think of how exactly we would be able to make our application usable for illiterate people, we used that as a basis of the overall design. The result was a design heavily based on images and also taking from the Domino’s build a pizza application. We have four steps for the user to go through to create their event.

  1. The user picks their charity and will see the logo and name appear in the event snapshot. If the charity is not in the database, only the name will appear. In this case to ensure that there is some business filtering at this step, we ask for the category of the charity. A small icon will appear in the snapshot to show the category picked.
  2. The second step is labeled event types but it’d be more appropriate to call it event themes. The user will be able to select what type of event they are planning to hold based on different themes. In this case Bartholomew would select cooking and competition. Our thought is to populate this list by popularity and add more images if the requests come in.
  3. The third step just allows the user to fill in the logistics of the event, like location, date, and size.
    1. Many businesses prefer to donate to local causes so it’s important to filter businesses by location.
    2. Depending on the business size they require requests to be made a certain time before the event is to take place, so date is required to filter out businesses that cannot fulfill a request with short notice.
    3. When size is chosen the snapshot will populate with people according to the size chosen, and it will help to filter businesses that may not be able to make donations for a certain size event.
  4. The forth step involves details about donation requests. This is the most optional step, but will help to narrow down businesses if filled out. There is a slider to choose donation value and images that can be selected to show donation type. As before images will populate the snapshot according to values chosen.

The user would then click create to make the event, and the next page would should a gallery of businesses that fit the event criteria. The businesses are arranged similar to the cover flow that mac uses. Again it would be mainly image based with symbols indicating business type, etc. There would be a short description and contact information for the business. At the top left you will see there is a help button. This is to address the case where the user does not know how to pitch to the business. The user will be led through a series of questions to outline their business pitch.

Analysis

This interface is pretty learnable because all the images should be fairly standard and the design takes on themes that are already present in many other places. The efficiency is pretty good because there is little reading and mostly just images. The only issue is that you have to step through all steps before you can get to the business suggestions. There could also be a way to view all the chosen businesses in a list to see all information in one screen. The drawings do not show a back button, but to increase safety we would add one to allow the user to go back and change information. Other safety issues would be addressed by the user being able to click again to select a certain feature.