WAP / Mobile mail

Jan 2007 - Jan 2008

Project Description

With the update of the new desktop version of AOL Mail, we needed a new version of WAP Mail that would reflect the changes we made within the desktop experience.

Contribution

I conducted research on the behaviors of our current WAP users, as well as research on what industry technology was available to us for use on our product. It is this research that helped allow us improve our UI for Version 2.0 of WAP Mail. Even though there were existing WAP products out there, this was new territory for our team. Upon inheriting the draft UI, I worked with the Mobile team to plan multiple usability tests and to successfully complete the UI .

  • Screeshots of Mobile Mail:
      
  • Wireframes of compose and search UI:
      

Learned

Initially I thought that working in the WAP / mobile world would allow me to design for cutting edge technologies. Instead, I learned that mobile interfaces require the most basic fonts, colors, and layouts. Ajax technology was not available and the amount of JavaScript used had to be minimal. I learned that designing for mobile technologies was great practice for designing with simplicity in mind.

Highlights

  • I learned how to design for WAP / mobile interfaces, and learned that it is MUCH more complicated than designing for the desktop environment. I was told there are thousands of browser types, and it made me appreciate IE, FF, and Safari dominating the web world. I had fun working with a medium that could be accessed anywhere.

Go to WAP Mail | List of Products | Next Project: WAP Calendar

WAP Calendar

Jun 2007 - Jan 2008

Project Description

After our initial efforts with the second generation of WAP mail, we began moving forward with the Calendar feature. Along side of Calendar, we also packaged it with a To-Do feature.

Contribution

Throughout the project, I was able to leverage my knowledge that I learned from working on the webmail version of Calendar and WAP / Mobile Mail. This helped me to quickly come up with UI concepts/designs and reduce design bugs.

  • Wireframe for wap calendar:
      

Learned

This project used the scrum project model. It is interesting and challenging to come up with a design and see the actual coded interface within a short period of time. I personally felt that scrums are more optimal when UI is given more iterations, and doesn't end up preventing the UI from changing.

Highlights

  • This project was very challenging due to technology that crossed the platforms of low to high-end devices.

Go to WAP Calendar | List of Products | Next Project: AOL Sync