42
Re-examining Design for Open Hardware Dave Vondle, IDEO Open Hardware Summit 9/22/10 Monday, September 27, 2010

Re-examining Design for Open Hardware

Embed Size (px)

DESCRIPTION

In the context of open source hardware, the designer must embrace openness in a way unnatural to our training....give people a platform, and sit back and watch them play! What needs to happen in open source hardware is a democratization of design on every level. We need to rethink our process, point of view, and role in design to reflect a platform approach that pulls cues from open source software.

Citation preview

Page 1: Re-examining Design for Open Hardware

Re-examining Design for Open HardwareDave Vondle, IDEOOpen Hardware Summit 9/22/10

Monday, September 27, 2010

Page 2: Re-examining Design for Open Hardware

The BUGbase UI exploration

Monday, September 27, 2010

Page 3: Re-examining Design for Open Hardware

the challenge

A short two week exploration into the main UI for the BUGbase module.

The goal was to !nd ways to make the BUGbase more delightful, understandable

and immediately more usable right out of the box without increasing the cost of the

unit signi!cantly.

what is buglabs?

A new kind of hardware company that aims

to allow a new generation of engineers to

express their creativity and build any type of

device they want.

Make mashups as applicable to hardware as

it is to web services.

Monday, September 27, 2010

Page 4: Re-examining Design for Open Hardware

process vs product

in many ways the process of designing in the open, sharing everything, was as interesting as the

product design itself.

• extreme collaboration

• rapid feedback

• public missteps

see all the gory details: https://client.ideo.com/buglabs/

Monday, September 27, 2010

Page 5: Re-examining Design for Open Hardware

Monday, September 27, 2010

Page 6: Re-examining Design for Open Hardware

comments on the first blog entry(first 2 days)

...

Monday, September 27, 2010

Page 7: Re-examining Design for Open Hardware

comments on the first blog entry(first 2 days)

...some ideas...

Monday, September 27, 2010

Page 8: Re-examining Design for Open Hardware

Mid-Project Concepts

Concept 1

Electronic Ink over Tactile

Switches

Concept 2

Color LCD with Capacitive

Touch

Concept 3

Monochrome Matrix LCD w/

Multicolor segmented backlight

Concept 4

Customizable Illuminated

Buttons with Side panel

Concept 5

NTE Microdisplay with

Trackball

Monday, September 27, 2010

Page 9: Re-examining Design for Open Hardware

Concept 4 - LED Tactile Switches with side status displayicon strip:paper or printable “transparency”

material permits user-customized icon

sets.

button faces:button fronts join with button tree to

form slot for icon strip.

tactile switches:mounted to mainboard button tree:

tree provides mounting surface for

button faces, rear of icon strip slot,

and !ex members for tactile switches

Monday, September 27, 2010

Page 10: Re-examining Design for Open Hardware

Concept 4 - Interchangeable Printable Icon Sheets

drop-in loading:full strip drops into button bar slot for

simple change-out

included icons:default icon set may include basic

functions or “numbered” buttons to

support out of box use.

Monday, September 27, 2010

Page 11: Re-examining Design for Open Hardware

Concept 4 - Icon illumination

tinted button fronts:optional tinted plastic can make

buttons “disappear” when not backlit

Monday, September 27, 2010

Page 12: Re-examining Design for Open Hardware

Concept 4 - Button illuminationbutton illumination:adjustable color/intensity illumination

can be used alone to indicate button

status or function.

Monday, September 27, 2010

Page 13: Re-examining Design for Open Hardware

Concept 4 - Icon illumination icon illumination:icon backlighting can delineate

groupings of connected button

functions or highlight active buttons.

Monday, September 27, 2010

Page 14: Re-examining Design for Open Hardware

Concept 4 - Interaction Design

Separation of functional areas: Status, User, Connectors

Pros

• simplicity

• in!nitely customizable labeling; high resolution graphics

• overt interface; visible buttons, tactile feedback

• glanceable

• does not compete with modules

• obvious boundaries of functionality

Cons

• multiple apps or multiuse scenarios ill suited

• minimal ability to display information

• single level of depth; no menu structures possible

Monday, September 27, 2010

Page 15: Re-examining Design for Open Hardware

Concept 1 - Fixed Segment Electrophoretic Display w/ Tactile Switches

tactile switches:mounted to main board eliminate

daughterboard PCB. provide tactile

feedback for button presses.

!xed-segment electronic ink:!exible "xed-segment electronic ink display for

high contrast. custom 23 segment per letter

font for readability and brand distinction

load distributing plate:improve button feel and distribute

load from tactile switches over a

larger area.

tactile bumps:provide an affordance for locating the

tactile switch below

Monday, September 27, 2010

Page 16: Re-examining Design for Open Hardware

Concept 1 - Interface

Monday, September 27, 2010

Page 17: Re-examining Design for Open Hardware

Concept 1 - Interface

Monday, September 27, 2010

Page 18: Re-examining Design for Open Hardware

Concept 1 - Interface

Monday, September 27, 2010

Page 19: Re-examining Design for Open Hardware

Concept 1 - Electronic Ink Segment De!nition

comments about interaction design for Concept B

• !xed segment limitation; 4 characters per button

• !xed number of buttons (8)

• menu structure and navigation challenges

• information retained without power

• high contrast

• no illumination

Interaction Flow

System Menu Map

Monday, September 27, 2010

Page 20: Re-examining Design for Open Hardware

Reflections on an Open Design Project

Monday, September 27, 2010

Page 21: Re-examining Design for Open Hardware

Reflections on an Open Design Project

Know your audience, communicate in their language.

Monday, September 27, 2010

Page 22: Re-examining Design for Open Hardware

Reflections on an Open Design Project

Know your audience, communicate in their language.

Ideally, be your audience

Monday, September 27, 2010

Page 23: Re-examining Design for Open Hardware

Reflections on an Open Design Project

Know your audience, communicate in their language.

Ideally, be your audience

Be prepared to dedicate 20% of your time to documentation and collecting feedback

Monday, September 27, 2010

Page 24: Re-examining Design for Open Hardware

Reflections on an Open Design Project

Know your audience, communicate in their language.

Ideally, be your audience

Be prepared to dedicate 20% of your time to documentation and collecting feedback

Openness supports rapid communication

Monday, September 27, 2010

Page 25: Re-examining Design for Open Hardware

Reflections on an Open Design Project

Know your audience, communicate in their language.

Ideally, be your audience

Be prepared to dedicate 20% of your time to documentation and collecting feedback

Openness supports rapid communication

You don’t own your design, everyone does

Monday, September 27, 2010

Page 26: Re-examining Design for Open Hardware

Reflections on an Open Design Project

Know your audience, communicate in their language.

Ideally, be your audience

Be prepared to dedicate 20% of your time to documentation and collecting feedback

Openness supports rapid communication

You don’t own your design, everyone does

Community doesnʼt come easy or free

Monday, September 27, 2010

Page 27: Re-examining Design for Open Hardware

Reflections on an Open Design Project

Know your audience, communicate in their language.

Ideally, be your audience

Be prepared to dedicate 20% of your time to documentation and collecting feedback

Openness supports rapid communication

You don’t own your design, everyone does

Community doesnʼt come easy or freeCommunication and contextualization takes care

Monday, September 27, 2010

Page 28: Re-examining Design for Open Hardware

Reflections on an Open Design Project

Know your audience, communicate in their language.

Ideally, be your audience

Be prepared to dedicate 20% of your time to documentation and collecting feedback

Openness supports rapid communication

You don’t own your design, everyone does

Community doesnʼt come easy or freeCommunication and contextualization takes careProfiting from a community is delicate

Monday, September 27, 2010

Page 29: Re-examining Design for Open Hardware

Reflections on an Open Design Project

Know your audience, communicate in their language.

Ideally, be your audience

Be prepared to dedicate 20% of your time to documentation and collecting feedback

Openness supports rapid communication

You don’t own your design, everyone does

Community doesnʼt come easy or freeCommunication and contextualization takes careProfiting from a community is delicateAsynchronicity is a 24/7 team member

Monday, September 27, 2010

Page 30: Re-examining Design for Open Hardware

Reflections on an Open Design Project

Know your audience, communicate in their language.

Ideally, be your audience

Be prepared to dedicate 20% of your time to documentation and collecting feedback

Openness supports rapid communication

You don’t own your design, everyone does

Community doesnʼt come easy or freeCommunication and contextualization takes careProfiting from a community is delicateAsynchronicity is a 24/7 team memberBrutally honest feedback improves quality

Monday, September 27, 2010

Page 31: Re-examining Design for Open Hardware

Monday, September 27, 2010

Page 32: Re-examining Design for Open Hardware

Monday, September 27, 2010

Page 33: Re-examining Design for Open Hardware

Monday, September 27, 2010

Page 34: Re-examining Design for Open Hardware

Monday, September 27, 2010

Page 35: Re-examining Design for Open Hardware

Monday, September 27, 2010

Page 36: Re-examining Design for Open Hardware

Monday, September 27, 2010

Page 37: Re-examining Design for Open Hardware

Monday, September 27, 2010

Page 38: Re-examining Design for Open Hardware

Monday, September 27, 2010

Page 39: Re-examining Design for Open Hardware

Monday, September 27, 2010

Page 40: Re-examining Design for Open Hardware

Monday, September 27, 2010

Page 41: Re-examining Design for Open Hardware

Monday, September 27, 2010

Page 42: Re-examining Design for Open Hardware

What does this mean for Designers?

Look to successful open source software projects, many times there is a lead architect who creates a framework, or platform that enables others to participate. This same person usually manages the project trunk to steer the project

The trunk can exist to fulfill general needs or act as a higher volume, lower cost object by leveraging economy of scale

The branches can fulfill certain “Long Tail” needs, as a configurable options or modifications of the trunk. (Peter’s example of design for vision impaired)

Platform Design

We must challenge ourselves to let go of the reins, and put our talents into enabling the community to work productively with us. Together we can create objects that hold a new kind of relevance that can only emerge from a collective process.

Let go

Monday, September 27, 2010