Design
Features, Wireframes, Navigation
Using the persona as a resource to pinpoint the traveling “needs” to be addressed by the mobile application, we steadily evolved an overall design through sketching, discussions, and brainstorming, ultimately producing a flow diagram and scenario.
We quickly decided on a map-based system, precisely because the target users very much were in the context of physical space, needing information in reference to location and proximity. Thus, we also depended on GPS functionality to orient the user on this map constantly.
Beginning from the concept of a map that automatically centered on the location of the user, we then began to brainstorm functions that would help our persona in her traveling experience. Our young and active persona demanded several kinds of information, general to any tourist—such as bus stops or hospitals—as well as specific to her interests—such as the safest bicycle routes and bicycle repair locations. We thus created a “layers” capability that could toggle on/off this type of information over-layed on the map. Such layers could automatically download once in a specific city, or could be manually downloaded by the user.
The second prominent function we addressed was the ability to record on-the-spot data—sound, picture, commentary text, that had location information attached, and then beyond that, be able to “forward” such pieces of information to others. This function was derived from several aspects of our directed storytelling and interviews: many travelers wanted to know things by word-of-mouth—directions, good restaurants, friends’ recommendations—however had no way to record it (besides pencil and paper or carrying a laptop with them) as they were out and about.
Furthermore, and as is characterized by our persona, the recording of such data and the sharing of it coincides with a social sharing phenomena we saw from many of our interviews: visitors asked (and trusted) friends for recommendations, visiting cyclists depended on the local cycling organization of the area to advise them on optimal bike routes and stops. Thus, our second function grew from this idea that previous travel by a friend, peer, or acquaintance could inform or enhance the present travel of another in a novel way through shared location-specific data, i.e. “memories”. We thus, created the capability to “mark” places on a map as you happened onto them—by picture, sound, or text—and save them for yourself or for friends.
Once the primary functions of the application were created and crafted a scenario around the persona to demonstrate these functions (see Scenario Development), we then worked on how these functions could be accessed with our 5-directional keys and two soft keys in conjunction with flow diagrams and wireframe development.
In terms of navigation, we tried to keep in mind that transitions between screens/functions would have to be fast with minimal button-hitting, keeping in mind feed-forward and feedback visibility. Also, we kept a consistent format that “back” buttons occurred on the left, while functions that brought you deeper into a menu or function showed on the right. We also kept in mind the standard button and feature sequences that existed on current phones (where is the phone book, when does it show up).
Scenario Development
Having determined our primary capabilities for the mobile application, we developed a scenario that would utilize our persona and exhibit the mobile need of collecting context-specific information and location memory-sharing.
Our persona influenced the development of the scenario by controlling several factors:
- Intrusiveness—our persona is a “wanderer” who relies on interpersonal face-to-face communication and avoids over dependence on the phone. The scenario would have to illustrate subtle, but powerful capabilities.
- Exploration and discovery—to that end, our persona also liked immersing herself in the environment and experiencing the unique; the scenario would need to exhibit this aspect of exploration and discovery.
- Memories—our persona had an urge and desire to share, remember and learn from the things she happened upon while traveling; the scenario would need to offer our persona the opportunity to capture a moment, space, or thought to be remembered.
Feedback from presenting this first scenario pointed out that the persona and the situations involved did not represent a strong enough need for the mobile capabilities of our application. Also, the persona was not consistent enough to bring the use of the device in the scenario to a reality—the story we told was very much coincidental. The scenario split the two illustrated functions of the application in a way that they did not seem integrated together—they might as well have been two different applications on the same phone. Thus we would work from that point on to create a scenario that encapsulated a real use with a vivid persona.
Our second scenario focused on one function—the discovery of a “mark” while our persona was wandering around Detroit, Michigan. This scenario was used for think-aloud usability testing.
Upon review, this scenario showed adequately the discovery aspect of our application, however did not represent the creation—“memory-making”—capability of the device, which is just as important. We then added to this scenario an additional situation where the persona would be able to create a map “mark” as she wanders the city of Detroit, and then discover another “mark” made by a friend.
