Note to self: shortcuts: < > ctrl-= alt-w
Meanwhile, I think an instructable a week sounds like an excellent plan for Spring semester senior year.
http://web.mit.edu/21w.789/www/syllabus12.html
quick feedback — get mvp out within weeks of idea, can see things not see in lab — fit into daily life, creative uses of app
mvp should address specific question or test experience
social groups — if it’s social app, make sure alpha users are friends
public betas — can have feedback button
but this mvp proto — usu friends sending emails
people do not accurately report how often they do things — instrumentation is important –VCs look for number engagements, number of mins of engagements per day. and for our own understanding.
can have voicemail daily or weekly depending on length of study.
talk to them as quickly after use as possible
for story finding, call researchers right after find story, and parents call after get comms with children
if creating content, use content analysis
processing data — affinity analysis, statistical analysis if lots of data
good example: civic content — about cities and governments: what was style of story telling, how long ago story occurred.
instrumentation and app analytics – features used or not (if not exposed to user) — see problem and then use qualitative method to understand why problem exists
power of combining = what and why people use system
facebook analytics team blog is very interesting. google is famous for this a/b testing.
this is a whole career. sifting patterns out of data.
einmann (sp?) elctures are very interesting.
contextual inquiry — h&r may be most relevant to this, where they watched people do taxes — improved online tax system to be more helpful. think aloud = can learn what people are thinking at the moment.
Experience Sampling Methods
how does all of britain spend their time? ?__? and how it changes over time (watch tv, read books). used to call people so have data for 50s, 60s (time on domestic acctivities has completely plummeted thanks to dishwashers etc). also studied location privacy / location fidelity –> learned likely no algorithm will solve this (e.g. buying a surprise gift etc.)
would people lie about locat? no usu. just say busy.
regardless should prolly always do semi-structured interviews
to understand where data comes from. vs structured have set list of questions
use specifics, not generalities
robust
multicast for new updates — sent repeatedly
wifi access points –> drilling stadium walls to run wires
enterprise class phone — okay to drop on floor etc.
researchesr were the ones producing the updates
controlled access area — so can get phones back
initially thinking rental where people can rent phones during game
other researchers watch people using it
after goal, during midtime, after game = spikes in use
final cut pro -> cannot handle four goals in last ten minutes (fans expect <30sec latency)
^– focus on that. want different angles, commentary
created app now 5 secs to edit, <30 secs to user.
===
2005-06 data plans not common
made sure people recruited had unlimited texting
reading contact dbase hard back then
big battery vs. writing algorithm to optimize energy use
to users mental model -> wrong, locations versus large locations
get broad group as possible (altho may be difficult for this class) but for hci paper publishing
corporate research lab -> if paying them, they may be very positive to you, and talk about it to friends is much more telling
===
hours-long prototype
send text messages when people play song – init and artist/song
recruited close friends with diverse music tastes
(they primarily play music on desktop at time) yep primary devices
depend on country whether require payment as a corporation — can just be pizza
tell them –> getting paid no matter what, use it like any other app you downloada
spacehold,
the plan: daily email manual log, vs instrumentation of android (tech accuracy)
location sharing experience — prefrosh at CPW (ask them to email us / survey those who come to build party)
http://web.mit.edu/21w.789/www/syllabus12.html
http://web.mit.edu/21w.789/www/notes/designnotes.pdf
a semester compressed into 3 hours
UX design, IxD, Industrial Design
Going from Interaction Design to Interface Design
Modelling:
We are defined as mobile application. How does it relate to someone’s life?
Why not jump straight into making it?
* Define if need to get information from elsewhere
* e.g. weather and stocks
* Drawing a picture -> extremely powerful for getting on same page
Also, show in 5 to 10 minutes to people who decide future of your project
Examples.
HCI: using metaphors. 2007: future of the phonebook?
2007: motorola owned the phonebook. and we were a walled garden (no things from other mftgs). mostly own own OS and had a lot of control. some look into social networking. realize that things may be beginning to change. when talked to people, not envision phonebook but rather friends. google was working on android, iphone come out but very app-based. motorola supporting 8 different platforms at time.
more hubs and spokes.
before and after metaphor: how does it make people’s lives better?
at the time, had to do everything manually. type in each person’s phone number. After: hope to make it more like learn what friends up to than management heavy.
3rd mental model: how do people think about the people in their lives? how did they cluster / organize them? it is an anthropomorphic well-known phenomenon that they validated with their own data collecting.
2007: can be able to manually form groups. But wanted a much more fluid structure. > favorites. go from 30 contacts avg to 300, 400, 500 > how to manage that information.
How to integrate data from other sources (not happen at the time)?
Model: determine who need to ask to do work (flickr, yahoo, etc.) -> diagramming it
Content types: from demanding to … patient ones… how to give Content a Behavior on a device.
User type: students, faculty, everyone (?___? hard to design for but common e.g. for weather)
Motorola has common archetypes of people (amalgated from real people). Very specific: what devices, what media, their life story. A lot of back and forth, but now fairly fixed ACROSS projects –> but does depend on the type of project. Segmentation of people. Have twelve (making whole device, not just an app!). From leading edge people to …
administrator often forgotten -> are the views / behaviors of your system different?
so for us, maybe lump all students together.
^– more high level
===
structure, flow, and process:
In reality: do go back and forth, since when have an idea hard to not sketch it out
undoing wireframes is expensive and tricky
also at information architecture: business owner, designer, and engineers all agree at use cases and use flows. Explicit among stakeholders -> saves a lot of money. Esp since once people see screens, engineers can get very attached to them. so efficient to get buy in earlier on.
For world today (not in 2007) there are fairly standard operating systems.
understand conventions of OS working with
iOS: very clear and approved guidelines
Android: less wild-west, ice cream sandwich: much more codified how it will look / interact: google suggesting will look better like ice cream sandwich
Where does back button? Android: hardkey, iOS: softkey at top.