Interaction Design


Puzzleye
product design

eXchangeFun
web application design

Web GIS
web application design

The bee
museum exhibits experience design

Explorability
strategic design

UReader
software design

UReader

Most RSS readers are a place where all the subscriptions are centralized. But you can only see the copy of the contents that are out of their original contexts. If you want to write comments, hear the background music, or see if your friends have changed blog visual theme, you have to get away from the reader and go to the actual site. And if you start browsing from there, the RSS reader will lose track of what you’ve read and what you haven’t. In short, the current RSS readers do not provide a seamless reading experience. We designed UReader, a RSS reader that integrates into your browser, to provide a seamless reading experience and full enjoyment of the actual context of subscriptions. We also further designed the iPhone version of the UReader.

Design Team:
Casey Addy, Cheng Fan, Heiko Maiwand, Yujia Zhao

Timeline:
2 weeks, fall 2008

Resonsibilities:
personas, concept development, paper prototype, wireframing, usability testing

Methods, Skills & Tools:
Personas, prototyping, wireframing, Photoshop

Deliverables
task flow (see image below),prototype, design specification(including wireframes)

Problem Space

Many people use RSS readers to view subscribed blogs. If you just want to get a sense of the posts, this kind of reader is adequate. However, often you want to understand the context of a post. What were the previous posts? What did others say about it? What if you want to write a comment? You must leave the reader and enter the actual blog, forum or other RSS sources. You may navigate from there, but now you‘re disconnected from the reader. The reader may lose track of what you‘ve seen and what you‘ve read, or so it seems. The design challenge was to provide users with seamless experience between reader and content, to not lose context, to let the reader better keep track of users’ viewing, and to adapt the reader into the iPhone environment.

Finding the Core

The problem space evoked many important questions to answer: what does the ‘context’ actually mean? What is ‘seamless experience’? What context do we need to provide in the RSS reader? Previous posts? Comments? Background music? Do we have to provide it in the reader?

We discussed our own RSS reading experience and what seamless experience means, as well as generated many concepts along the way. We agreed upon that we need to enhance and facilitate actual reading experience in the actual websites by making the Reader an “ambient” tool, rather than taking users away from the actual posts in real web context. But our design should also support the use of RSS reader as a traditional feeds centralization place.

go to the top

Concept Development

We developed personas to help with concept generation. We continued to generate a wide range of concepts that address the core, from which the final concept evolved and emerged through discussion and critique. We developed this concept into our initial design, built paper prototype, and conducted usability testing. We iterated and developed our final design based on the user feedback, and made wireframes and mockups for the final design.

The final design UReader is a side-bar plug-in of web browser. There are category tabs on the left to organize feeds. Within each category, accordion structure is used to open and close different feeds sources. Each feed is shown as a title and a brief digest. Clicking each title or digest will bring users to the actual post. In the actual site, there are in-situ hints to keep track of reading while not distracting users. If UReader is maximized, it will occupy the browser and work as a traditional RSS reader where only content is centralized and shown without context. This gives users the flexibility of use. click here for click-through prototype.

go to the top

concept sketches

paper prototypetask flow

wireframe of main interface

Adaptation to iPhone

iPhone platform is a different environment with its own constraints, advantages, and characteristics. In order to adapt the UReader as an integrated part of iPhone environment, we need to take advantages of what iPhone plartform provides, work within constraints, and make the visual and interaction style of the UReader consistent with iPhone platform. The key aspects of iPhone environment we identified were limited screen space, touch screen with gesture-based interaction, and unique Internet browsing experience. We generated sketches that modify and adapt the Reader into iPhone environment. We changed accordion organization into cascade menu flow just like common iPhone application menu, and changed “in-situ” hint into blue dots according to the typical visual style of iPhone application. We developed wireframes and high fidelity mockups.

go to the top
wireframe/task flowUI mockups/task flow