Minnutes
	· Kodak logo is usually the admin button (double click)
	· Kiosks already have a "color chooser" app, but ours is close
	· Cutout shape ideas
		§ Present rectangle and have a control panel to size is, and drag to move
		§ Everyone likes arrow keys
			. a lot of repeated pushes (no one thinks of holding)
			. Sound feedback can get annoying
	· Heart & shape recognition
		§ If it's recognized, how do we know what to do next?
		§ Remember the Soccer Mom example (only 80% of the population can be pleased)
			. Generally no dragging, more buttons than dragging.
				¨ No one thinks of dragging
				¨ Only techies know what "dragging" is
				¨ Use buttons
			. Double clicking is rare, too
		§ System needs more feedback
			. "Touch the center point of the heart"
			. No harm if the shape is automatically recognized, but having 2 options isn't very smart
	· "It is easier to critique designs that create them"
	· All pictures at once
		§ Move images by 4's
		§ How will you know about the dragging feature?

	· What happens if you take more than one picture when choosing the background image?
		§ Apply things like that to the whole process, keep it consistent
	· Wizard-like interface would probably be best
	· Only have about 7 chunks of information at once
		§ Lighten up the screen, focus only on what the user is going to be doing
			. Only expose the least amount of tools
				¨ Hide sizing and rotating for instance
				¨ Sliding up and down is annoying
			. Advanced users will go hunting for their more advanced features
				¨ Choose automatic images
					. Undo, Print, Add label, add & remove image, add label
					. "Extras button"
	· These people are probably thinking pictorially
		§ "You can make one of these"
		§ Choose pictures up front
			. "Pick a few to work with"
		§ Maybe join the cropping with the movement
			. WYSIWYG works best
			. See the background real-time when you're choosing it
		§ Requirements say that it has to exist, not that it's easy to find
		§ WSFTP button in the middle of the divider to add
		§ Put 40% whitespace around things
			. Check it in German for the worst-case scenario
	· Important points to have:
		§ Intuitiveness
		§ Discoverability
		§ Learnability
		§ Redundancy, have a simple, obvious way and an advanced way as a backup
	· How to we get the images?
		§ Needs loading interface
		§ Smoke and mirrors will be good
			. Just pull them from some directory
		§ Let them choose the images and then forget about choosing the images
		§ How do we know how we want them cropped until seeing the final menu?
			. Crop them later.  A lot of people are going to be changing their minds
			· I have 30 images, I choose one, how big is it and where does it go?
			· Do we need to go to full resolution when cropping?
		§ Force them into a workflow
			. Click picture -> Popup "How do you want to cut it?" -> put on the canvas somewhere
		§ Put some instructions on the canvas
			. Touch picture to choose them
			. Demonstration animations/slideshow
		§ Try and find examples and take credit for them (watch out for patents)
	· How do we test?
		§ Find the target audience
			. Human experimentation can be bad
				¨ "We aren't testing you, we're testing the system"
				¨ Give them the solution at the end
		§ Think up some metrics
			. Design the test from there
		§ 5-6 should be sufficient
		§ Look for
			. Efficiency
				¨ Error rates
				¨ Task time
				¨ Time spent in error mode
				¨ Task completion rates
			. Limit by the "I've had enough of this!" factor
			. Don't say the keywords in the task (it's cheating)
				¨ Find funny ways to say things
				¨ Be vague
			. Offered help for scripting up the task
Damien's law of usability:
	"If you don't allow users to make a mistake, they can't."