Mobile Media Asset Management (MMAM)

2005.01.24 SLIDE 1DMDS – Spring 2005

Mobile Media Asset Management

(MMAM)

2005.01.24 SLIDE 2DMDS – Spring 2005

Presentation Outline

• Project Idea/Overview

• The Goal

• Motivation

• Target Audience

• Our Team

• Current Status

• Our Plan

• Problems

2005.01.24 SLIDE 3DMDS – Spring 2005

Presentation Outline

• Project Idea/Overview

• The Goal

• Motivation

• Target Audience

• Our Team

• Current Status

• Our Plan

• Problems

2005.01.24 SLIDE 4DMDS – Spring 2005

Problem Statement

• There are a lot of camera-phones out there, with a lot of photos, being taken. But…– Difficult to get photos off phone– Multiple apps competing for photos (mobile, desktop,

web) – Organizing and retrieving photos is difficult,

particularly on a mobile device– Need for easy annotation of photo at time of capture– Privacy and Cost are important, but difficult to

understand

2005.01.24 SLIDE 5DMDS – Spring 2005

Mobile Media Information Flow

To other mobiles via MMS

To photo sharing sites/blogs

To desktop PC via Bluetooth/USB

To email

To print service

2005.01.24 SLIDE 6DMDS – Spring 2005

Overview of Existing Solutions

• Strengths– Tags– Timelines– Mobile posting to multiple destinations– Privacy settings

• Weaknesses– Synching– Interoperability among apps– Metadata loss

2005.01.24 SLIDE 7DMDS – Spring 2005

The Solution?

• Create uniform interface (both conceptual and graphical) for routing photos from phone to a variety of services and destinations– Tag based organization/retrieval– Feeds– Photo tracking– Layered interface : starts out simple, but user

can dig in to reveal more details

2005.01.24 SLIDE 8DMDS – Spring 2005

The MMAM Prototype

• Though there are many implementation challenges, UI is our primary focus– Limited screen space, limited user attention, and poor

input capabilities on devices

• Features we need to test early in Prototype:– Tag-based organization and retrieval interface– Example feeds– Keyboard-driven UI – don’t want too much navigation

via scroll wheels, joysticks, etc.– Cost-aware routing– Simple annotation interface

2005.01.24 SLIDE 9DMDS – Spring 2005

UI Ideals for Prototype

• Keep phone interface as simple as possible, require as few clicks/actions as possible

• Make use of default behaviors, user profiles (configured on desktop companion application) where possible

• Desktop application (not yet prototyped)– Feed configuration– Profile management– Synchronization interface– More complex annotation and organization options

2005.01.24 SLIDE 10DMDS – Spring 2005

Prototype Design: UI

2005.01.24 SLIDE 11DMDS – Spring 2005

Prototype Design: UI (cont)

2005.01.24 SLIDE 12DMDS – Spring 2005

Presentation Outline

• Project Idea/Overview

• The Goal

• Motivation

• Target Audience

• Our Team

• Current Status

• Our Plan

• Problems

2005.01.24 SLIDE 13DMDS – Spring 2005

What questions do we want to answer?

• What current sharing behaviors and photo uses are problematic due to problems/complexities present in current technologies?

• What emergent behaviors might users be more likely to engage in if better supported by technology?

• How willing are users to adopt new camera phone technologies (hassles in working with prototype/pre-alpha technology)?

• Can we test our application ideas with thin (paper/Flash/Python) prototypes effectively?

• Why don’t people share more? (cost, complexity)?

2005.01.24 SLIDE 14DMDS – Spring 2005

What needs does it seek to address?

• Managing mobile photos (especially sync) is difficult. Current applications don’t interoperate well.

• Sharing is not seen as a need yet, but if simple sharing tools existed, would it be a need? (hopefully yes, and our app would address that need)

2005.01.24 SLIDE 15DMDS – Spring 2005

What are your project requirements?

Must:– allow organization and retrieval of photos (with tags?)– enable (or simulate) distribution of photos from device to PC,

individual, and at least one network photo service– allow tracking of distributed photos (at least until they exit the

system)

Should:– allow easy integration of received photos with users own

photo store (merge tags)– allow user to configure feeds to various destinations which

hide underlying transport protocols– allow creation of macros or shortcuts (even one-key photo

rating at capture time, or “annotate later” flag)

May:– manage storage space on device (e.g. attention driven routing

– rarely used photos get archived to PC)

2005.01.24 SLIDE 16DMDS – Spring 2005

Presentation Outline

• Project Idea/Overview

• The Goal

• Motivation

• Target Audience

• Our Team

• Current Status

• Our Plan

• Problems

2005.01.24 SLIDE 17DMDS – Spring 2005

Why do we care about this problem?

• Shane and Simon use camera-phones too much and know that sync and sharing are currently difficult.

• Want a better app for ourselves, assume other users have similar problems.

• Better share app could also improve MMM research.

2005.01.24 SLIDE 18DMDS – Spring 2005

What do we expect to learn from this project?

• More about prototyping mobile applications

• More about mobile user “needs”– How mobile photos (and networked cameras)

are used differently than other photos– The methodology for uncovering emerging

user needs. Which comes first: UI or task/behavior?

2005.01.24 SLIDE 19DMDS – Spring 2005

Presentation Outline

• Project Idea/Overview

• The Goal

• Motivation

• Target Audience

• Our Team

• Current Status

• Our Plan

• Problems

2005.01.24 SLIDE 20DMDS – Spring 2005

To whom does this solution matter? Why?

• This is mostly good for camera-phone users who have trouble with sync, sharing.

• Handset manufacturers, wireless carriers should also be interested.

2005.01.24 SLIDE 21DMDS – Spring 2005

How will we work with users in design process?

• Focus groups, design walk-throughs and interviews with SIMS (and perhaps other campus) camera-phone users.

• Test a variety of prototypes with the same users.

2005.01.24 SLIDE 22DMDS – Spring 2005

Presentation Outline

• Project Idea/Overview

• The Goal

• Motivation

• Target Audience

• Our Team

• Current Status

• Our Plan

• Problems

2005.01.24 SLIDE 23DMDS – Spring 2005

Who is on our team and what are their roles?

• Shane Ahern, developer/project manager(?)

• Simon King, system architect/engineering manager(?)

• Hong Qu, UI and Interaction designer(?)

2005.01.24 SLIDE 24DMDS – Spring 2005

How do/will we mange our team?

• Weekly meetings

• Biweekly status report

• DMDS and IS298

2005.01.24 SLIDE 25DMDS – Spring 2005

Presentation Outline

• Project Idea/Overview

• The Goal

• Motivation

• Target Audience

• Our Team

• Current Status

• Our Plan

• Problems

2005.01.24 SLIDE 26DMDS – Spring 2005

What have we done thus far?

• Formed core team

• Developed project concept and initial prototype (IS 246 final project)

• Identified potential faculty sponsors and developed initial project proposal

2005.01.24 SLIDE 27DMDS – Spring 2005

Team and resources needed?

• First year SIMS for project management and UI

• Need users as interview/focus group subjects

• Compensation for subjects?

• Software?

• Phones?

2005.01.24 SLIDE 28DMDS – Spring 2005

Presentation Outline

• Project Idea/Overview

• The Goal

• Motivation

• Target Audience

• Our Team

• Current Status

• Our Plan

• Problems

2005.01.24 SLIDE 29DMDS – Spring 2005

Key dependencies and risks

• Need time for interviews, user studies, prototype tests

• Could run into technical snags during development

• Might not be able to find users• Do we need permission to interview students?• Scope not yet defined clearly• Likely to have insufficient number of user

subjects, not a representative cross-section

2005.01.24 SLIDE 30DMDS – Spring 2005

How are we managing risks?

• Scope – defining in next two weeks• Start lining up SIMS students• Ask 213 students to help us?• Qualification Questionaire • Focus group develop personas and tasks

– What should we show to focus group – screen shots? Our java prototype?

– Marc’s undergrads?– Novice or advanced users?

• Development snags– Need proof of concept “hello world” app in java and/or

flash to identify technical problems early

2005.01.24 SLIDE 31DMDS – Spring 2005

What are our contingency plans?

• If SIMS or Marc’s undergrads don’t pan out?– Outside friends, other schools (Haas, EECS)

• Tech snags?– use PC, paper prototype

2005.01.24 SLIDE 32DMDS – Spring 2005

What are our unknowns?

• Do users want this?

• Will they comprehend “feed” concept?

• Will someone else solve this first?

• Unknown unknowns are unknown.

2005.01.24 SLIDE 33DMDS – Spring 2005

What design process will we use and why?

• User-centered design process*– Market Definition: define target audience and key

needs, identify competitors– Task Analysis: identify users’ goals and tasks,

understand current tools and problems– Competitive Evaluation– Design and Walk-through: walk through proposed

solutions with potential users– Evaluation and Validation: touch base with users on

evolving design

* from http://www-3.ibm.com/ibm/easy/eou_ext.nsf/publish/19

2005.01.24 SLIDE 34DMDS – Spring 2005

What are our iteration plans?

• Focus group develop persona evolve prototype user interviews & heuristic evaluations evolution of prototype

• It would be nice to show users two iterations of prototype after initial focus group…but time is short

2005.01.24 SLIDE 35DMDS – Spring 2005

Presentation Outline

• Project Idea/Overview

• The Goal

• Motivation

• Target Audience

• Our Team

• Current Status

• Our Plan

• Problems

2005.01.24 SLIDE 36DMDS – Spring 2005

Questions we would like help with

• Focus group:– how do we recruit?– how much of prototype?– what types of questions?– when in process? (immediately, or develop better prototype first)

• Scope: – Is it better to make this a user needs (what do people want)

project?– Or try to develop functional prototype and test with users in field

• What questions need to be answered before we starting coding a working prototype?

• Catchier (or more accurate) project title?