Manufacturing 101: Prototyping -- MFDs
In the previous post, I critically analyzed the multi-function devices being used at Wellesley and one of the most popular noted issues with these machines is the existence of poor mapping in the touchscreen and the keypad. Hence, I decided that the prototype of choice would be a new interface for those features of the MFDs, helping students and faculty navigate them.
In designing a new interface, I first thought about the many comments other students expressed to me. Also, while keeping those notes in mind, I went to the MFD in the Science Center and played with it some more, in order that I could have a more critical eye and notice the pros and the cons of the device. I also took measurements of the screen and keypad for future reference.
The first thing I personally noticed was how cluttered the screen looks and the lack of "common sense" functions and terms. Then, I turned to the complimentary keypad: it is abnormally shaped and holds several buttons placed inconveniently. So, I decided to make not only a touchscreen more user-friendly but also a keypad less dysfunctional, which translated into these key points:
In conclusion, I had a wonderful time designing this prototype and deciding on the type and features I thought would be best. In conjunction with my extensive research into the problems and incentives behind the MFDs in the previous class, I felt inspired to continue that project and really play with such an application. I am excited to see how my "brain child" turns out.
The first thing I personally noticed was how cluttered the screen looks and the lack of "common sense" functions and terms. Then, I turned to the complimentary keypad: it is abnormally shaped and holds several buttons placed inconveniently. So, I decided to make not only a touchscreen more user-friendly but also a keypad less dysfunctional, which translated into these key points:
- More space between buttons
- Log-In/-Out is clear and accessible
- Central functions (e.g. print, copy, fax) appear front and center on screen
- Only essential and back-up features appear on the keypad
- Improve aesthetic appeal
- Improve adaptability of screen to individual
- Keyboard feature is accessible, automatic and familiar
Those ideas were only a few with which I began and, as I developed my prototype, more were added and some were changed. As described in the assignment, the project needed to incorporate foam, cardboard and paper. I began to draw the main components of my prototype: screen, k
eypad and handle/swivel. From that, I decided that the screen would be composed of lighter materials (paper and foam) whereas the the handle would be made of cardboard -- a sturdier material for support. The keypad would be made via 3D printing as it was intended for the students to become familiar with designing such.
eypad and handle/swivel. From that, I decided that the screen would be composed of lighter materials (paper and foam) whereas the the handle would be made of cardboard -- a sturdier material for support. The keypad would be made via 3D printing as it was intended for the students to become familiar with designing such.
I began with a few sketches of how I want the screen to look and ended with two different designs. Whereas one interface is purely touchscreen, the other is designed to work with a modest keypad -- really designed as a back-up for those not comfortable with inputing data on the touchscreen. This prototype is a "look-alike," meaning it does not function as intended nor is it manufactured as intended. I wanted to produce a piece that others could interact with and visualize.
Beginning with the cardboard, I took about 5 pieces -- 2 to create rounded "poles," 2 to create a long arm and 1 as a support for the screen. With the help of double-sided tape, a lot of duct tape and glue, the handle was made. The foam board was cut by a hot wire into a a curved square block (approx. 10 in x 6.5 in); the paper used to portray the actual screen is roughly (9 in x 6 in). Flaps were cut into the bottom pole to act as a ground support.
The sketches made are detailed and show the different set-up (and components). However, out of this entire process, the most difficult and time-consuming piece became the computer design of the 3D keypad used for the 3D printer. In sketching my design for the keypad, I took note of the current functions and the students' comments. I concluded that if a keypad is to be used alongside a touchscreen, it must include -- and only include -- the essential functions for if there is a glitch in the touchscreen system and it must naturally attract the attention of the user.
Based on those principles and after several sketches, I decided that the most efficient keypad would include: a dial pad (with 1 corresponding to ABC as in the flip phone design); log-in/log-out button; a help button; arrows to scroll and select; and central commands (i.e. pause, cancel, start). In the last final minutes, I thought of the presence of screen settings for those who need more light or contrast and decided to add two small dials for those on the pad as well. It would be very difficult to access those features from the screen normally. Each of these buttons will be clearly labelled. Furthermore, to develop an aesthetic appeal, I wanted to modernize the keypad and make it more high-tech or futuristic. To do so, I used a lot of fine cut geometric shapes and mounted the main controls on a trapezoidal plane, which was asymmetrically mounted on the rectangular base itself. The base also had a side cut in the back to make it slant visually and also to follow the asymmetric style. I also intentionally allowed an open space in the top-right corner for user instructions/warnings to be placed by the library staff. That way, the individual is aware of the notifications and able to understand the functions available to him/her.
In conclusion, I had a wonderful time designing this prototype and deciding on the type and features I thought would be best. In conjunction with my extensive research into the problems and incentives behind the MFDs in the previous class, I felt inspired to continue that project and really play with such an application. I am excited to see how my "brain child" turns out.
I really like that you took what we worked on last week and adapted it to this week's project. Your idea is really great and it looks like it would greatly improve the user experience.
ReplyDelete