EDTECH 597: How Wind Turbines and an Old Viaduct Got me to Thinking About Better App Design

The user interface for my “No Texting While Driving App” for EDTECH 597.

I have said in my in-class forum posts for the EDTECH 597 mobile app design class that design must be more than just making something look pretty. It must also solve problems. However, I also know from my experience working in the newspaper business that good-looking design is important if for no other reason than to make people pick up and buy your newspaper or magazine. It is with this mindset that I approach the app class.

All Form and No Function…

What I have noticed is that very often my designs are heavy on pretty and not always so much on function. They’re not bad. They do work, but I just feel like I’m not yet emphasizing the UX UI (user experience, user interface) aspect of the designs as well as I want to—mostly because I don’t have a lot of experience in seeing how this is done—either from other apps or from design in general. There are a lot of great apps out there, but having not had a cell phone for several years has put me behind as a mobile app consumer.

But I found inspiration (or at least food for thought) this week on a site called Inhabitat.com. The story in question revolved around the need to redesign some old viaducts in the Italian countryside. The goal was to make them useful again and beautiful and to help revitalize the area through some environmentally conscious design using the existing structure. Additionally, the designers already had part of a structure to work with like we do with our mobile apps. They just needed to do something with what was already in place. The design highlighted on Inhabitat.com featured wind turbines that had been built into the support beams of the viaduct, making it look like a wall full of different sized clocks and giving it a funky 60s feel. And it was one of the most beautiful and practical applications of green design that I’ve ever seen. (Click on the red hyperlink in this paragraph to see it.)

The road and its supports already existed. It provided a partial framework for a project onto which the designers could add. Together, the viaduct structure and the wind turbines looked beautiful, so the design for this was able to meet my design criteria of the end product being both beautiful and able to solve problems at the same time. It had the added benefit of bringing two useful, but unrelated structures together in one structure. These are items that you wouldn’t necessarily automatically think would go together, but once they were put together, it was an “Of course!” moment.

The Hands Off App

As in the case of the viaduct, the usefulness of this week’s app design is already built-in, the beauty of the design is not. As I already mentioned in my design for the drawing app, I wanted to provide visual clues that tell the user what to look at even if they don’t have instructions to read. In the book, The Design of Everyday Things by Donald Norman, these types of visual clues are called ‘affordances.’ They are the visual clues that allow a person to know that a push-plate on a door means to push the door open instead of pulling it, that a knob means to turn and open, and a slot provides a place to insert something. It makes me wonder what—if any—affordances did the designers for the viaduct project see or maybe more accurately, see lacking and how did they land upon the design they did given the minimal parameters set forth by the beams of the viaduct?

So the question for me as I work on building this app beyond the basic prototype provided for us in the book is “What kind of visual affordances can I use to make this app more UX UI-friendly and still beautiful at the same time?” And more importantly, like the designers of the windmills, how can I use the structure of the design given to us in the book as the “No Texting While Driving” example and build on it so that it’s both beautiful and useful?

Reflections on HelloPurr, App Development and DC Comics, EDTECH 597 Week 3

I have found throughout the last several weeks of being in this EDTECH 597/ mobile app design class that I have a discrepancy in my skill sets. On the one hand, because of my background in traditional design—newspapers, magazines, etc—I can see the great potential in mobile apps and how they could help revitalize and change the design industry. On the other hand, since I haven’t owned an actual phone in several years, opting to use Skype on my computer instead, I’m finding that there’s a learning curve for the new technology. My computer can’t find the drivers to recognize my computer, I don’t always know how to retrieve my messages from my phone, apps that I really love take up a lot of my phone’s resources, etc.

As frustrating as this has been for me, it also occurs to me that the experience is useful. It will help me be more compassionate with clients as I work through the design process. Technology can be scary to people. Hopefully, the experience of doing this will enable me to better help them through the process of design.

It has also allowed me to look at the design principles that I do find valuable (from other media) and carry them over to app development. One stands out in particular, and that is the ability to click on an icon and be taken back to the main page of the app. Many of my apps don’t have this feature, and it frustrates me, because at this juncture I usually just have to go back to my phone’s homepage and try again. So far the one that frustrates me the most is the DC Comics app. It usually takes me down a maze with no ability to back track if I accidentally hit a wrong button. Since I love graphic novels and love DC in particular this frustrates me to no end. It also makes me wonder how it can be that organizations/ businesses like this that are design-oriented by the nature of what they do struggle so much when it comes to usability design. I guess it just goes to show that we all have blind spots in this age of ever-changing technology.

I was speaking to a friend of mine about this issue. He happens to work in instructional design, and he assured me that  I would learn this part of the design process in the course of my studies. He spoke about it in terms of user-interface design/ user-experience (UX UI). I have been exposed to this concept of design before in another class at the undergraduate level. It was the first time that I was introduced to the idea that design should be both pretty and functional, and I’m hoping to train myself to look for that element in design. While I learned in my newspaper days that design should actually look pretty, because it makes people stop and pick up newspapers (or read websites or try mobile apps in this day and age), it also should do something more. I will be mindful of that as I move forward.

Just for a visual record, the screenshot of my HelloPurr app is below.

HelloPurr app, assignment one in EDTECH 597, mobile app development class