Mobile Media Asset Management

1

• Mobile Media Asset Management
• (MMAM)

2
Presentation Outline

• Project Idea/Overview
• The Goal
• Motivation
• Target Audience
• Our Team
• Current Status
• Our Plan
• Problems

3
Presentation Outline

• Project Idea/Overview
• The Goal
• Motivation
• Target Audience
• Our Team
• Current Status
• Our Plan
• Problems

4
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

5
Mobile Media Information Flow
To desktop PC via Bluetooth/USB
To print service
To email
To photo sharing sites/blogs
To other mobiles via MMS
6
Overview of Existing Solutions

• Strengths
• Tags
• Timelines
• Mobile posting to multiple destinations
• Privacy settings
• Weaknesses
• Synching
• Interoperability among apps
• Metadata loss

7
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

8
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 dont want too much
  navigation via scroll wheels, joysticks, etc.
• Cost-aware routing
• Simple annotation interface

9
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

10
Prototype Design UI
11
Prototype Design UI (cont)
12
Presentation Outline

• Project Idea/Overview
• The Goal
• Motivation
• Target Audience
• Our Team
• Current Status
• Our Plan
• Problems

13
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 dont people share more? (cost, complexity)?

14
What needs does it seek to address?

• Managing mobile photos (especially sync) is
  difficult. Current applications dont
  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)

15
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)

16
Presentation Outline

• Project Idea/Overview
• The Goal
• Motivation
• Target Audience
• Our Team
• Current Status
• Our Plan
• Problems

17
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.

18
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?

19
Presentation Outline

• Project Idea/Overview
• The Goal
• Motivation
• Target Audience
• Our Team
• Current Status
• Our Plan
• Problems

20
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.

21
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.

22
Presentation Outline

• Project Idea/Overview
• The Goal
• Motivation
• Target Audience
• Our Team
• Current Status
• Our Plan
• Problems

23
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(?)

24
How do/will we mange our team?

• Weekly meetings
• Biweekly status report
• DMDS and IS298

25
Presentation Outline

• Project Idea/Overview
• The Goal
• Motivation
• Target Audience
• Our Team
• Current Status
• Our Plan
• Problems

26
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

27
Team and resources needed?

• First year SIMS for project management and UI
• Need users as interview/focus group subjects
• Compensation for subjects?
• Software?
• Phones?

28
Presentation Outline

• Project Idea/Overview
• The Goal
• Motivation
• Target Audience
• Our Team
• Current Status
• Our Plan
• Problems

29
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

30
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?
• Marcs undergrads?
• Novice or advanced users?
• Development snags
• Need proof of concept hello world app in java
  and/or flash to identify technical problems early

31
What are our contingency plans?

• If SIMS or Marcs undergrads dont pan out?
• Outside friends, other schools (Haas, EECS)
• Tech snags?
• use PC, paper prototype

32
What are our unknowns?

• Do users want this?
• Will they comprehend feed concept?
• Will someone else solve this first?
• Unknown unknowns are unknown.

33
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/p
  ublish/19

34
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 groupbut time is
  short

35
Presentation Outline

• Project Idea/Overview
• The Goal
• Motivation
• Target Audience
• Our Team
• Current Status
• Our Plan
• Problems

36
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?