Note to self: shortcuts: < > ctrl-= alt-w
Meanwhile, I think an instructable a week sounds like an excellent plan for Spring semester senior year.
Note to self: shortcuts: < > ctrl-= alt-w
Meanwhile, I think an instructable a week sounds like an excellent plan for Spring semester senior year.
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
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
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
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)
a semester compressed into 3 hours
UX design, IxD, Industrial Design
Going from Interaction Design to Interface Design
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
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.
Ways we screwed up:
Didn’t agree on research questions beforehand so when we talked to people in parallel fashion, we explored different topics (yay data that’s hard to affinity group), e.g. one of us talked to people about how they share projects, and someone else did how people who use location services, and someone else asked specifically about a keyholding (indicating when rooms useful to multiple people, that only some people have open/close access to, are open) app
I wrote summaries of each of my question instead of interesting quotes
MITERS survey summary
(talked to four people over an hour)
(# of people)
My notes from class:
typical study, 1500 to 2500 notes
this week: go from data to project (project due in 2 weeks)
contextual design –> how things flow between people, spaces. how to understand reactions. how to figure out bottlenecks. physical medium, information flow
Flow model – for music. (cds, cars, work, homes). Info flow: who talk to (significant others, not so much family members)
Conversation analysis — text logs starts and ends, requests. weilenmann — a paper. not allowed to call in fitting room – but perhaps texting would be okay.
crit incident analysis – used in usability analysis of existing products, or when beta
focus: grounded affinity analysis to organize large amounts qualitative data. Not! to prove / disprove theories. (because only talk to 3 or 5 people). design something to work with what i’ve observed for these datapoints.
affinity can be very large — covering walls of room. 2500 sticky notes.
affinity — a hierarchy – raw data, exact quotes/observations, photos,
Find similar problems -> group and label. Then group again.
Comes from science – hard to know all the hypothesis before in field. so instead bottom up, collect lots of data and then develop theories.
Each note — 1 or 2 sentences, single idea.
Not problem for us, but in large groups — hard to find notes! know it exist but in 1000…
colleague — camera + projector -> talk and it will highlight on wall where note is (search text)
Themes — common terms, often exact quotes useful b/c that’s the order they have to think about it today
In lab / research –> try to get diverse team (marketing, biz, research, engineers, designers) because each person approach data differently. 4 to 5, 6 max.
Think about research questions when starting out
And how perspectives might bias our interpretation (if already have idea of what want to build)
Read note aloud so everyone knows and agrees what sort of groupings
GT Data can be used for years and years — public in academic so people can use it.
BH standard in industry — miss a lot of what’s going on if just grouping own insights instead of actual data quotes
New concepts — quantity over quality (for us, 30 mins affinity, then 10 15 mins throw out ideas)
2500 data points
How to prioritize? e.g.
well, there is a long gap in my blogging
but to get back into the flow of microblogging / blogging everything, here is a screenshot of our first day slides from nanomaker, a class targeting underclassmen which I am randomly joining in as a junior.
Our first lab for this week is a CD spectrophotometer:
And we’re supposed to go through the intro to MATLAB:
6.131, Power Electronics, has been a blast, even if it’s completely destroyed any belief I have that I can build a functional circuit. Lectures are awesome and Practical Electronics for Inventors is and awesome and completely readable / understandable book.
Here are the main analogies I have learned through 6.131 in terms of relating power electronics to mechanical mechanisms:
Totem pole: because your comparator’s square wave cannot directly drive FETs (not able to source enough currrent)
Boost converter: (e.g. takes 6V and turns into 15V — usu. cannot get it to gain more than 1 order of magnitude). Like winding up a fishing rod (inductor charging capacitor while diode prevents cap from discharging back into inductor), build up power (pool fishing wire behind you), and then release (snap fishing rod forward).
(thus, do NOT hook up without load because it is like winding up the fishing rod and and whacking the wall repeatedly, over and over, at some kHz aka many times per second).
Buck converter: (e.g. takes 15V and turns into variable 0 to 12V). — a switching amplifier (linear amplifier, like 7805, dumps extra power as heat, while switching stores in cap for later use).
transformer trades off voltage and current like mechanical gearbox trades off speed and torque. also, by power conservation, (and used to measure parasitics / Lleak and Lmag), short one side of transformer = short other side, open circuit one side = open circuit other side.
–> todo: reflecting things across the transformer
regulated voltage — a wall wart http://www.ladyada.net/learn/powersupply/ counts, and then can be further filtered ala 2.007 nano carrier with as switching power supply
Also, circuit debugging things that 6.131 has taught me:
Getting crazy fuzzy on your 74HC delay circuit? (ringing) — check if you have bypass caps, both on your 12v and 5v rails. (For me, connection a cap across pins 14 and 7 didn’t work either, but dropping a cap across 5v rail worked instantly).
2125 debugging: does not required Vdd, merely requires Vcc and the inputs from the delay circuitry. Pin 2: input. Pin 7: output. On high side, measuring directly may not work (get fast flickering or no visible signal) — to measure high side output, stick probe gnd on pin 5 (gnd) and probe in 7 (output). Same for A (which cannot be measured without a load?)
Totem pole drawing max current when your high side signal from the delay circuit is plugged in?
Check that all the grounds are connected.
If you’re at MITERS, check that it’s not a sketchy scope probe / scope problem.
Do NOT build complicated circuits (e.g. control circuitry) straight on the protoboard, no matter how sure you are of building it correctly — you can spend hours and have a short somewhere and be hard-pressed to diagnose it or rule your control circuit out as the source of your [short, bug]. Build it on the breadboard first — it really is actually must better than protoboard, no matter any concerns about breadboard sketchiness, the faster prototyping time is definitely worth it.
Building the delays and 555s with unclipped resistors and caps may not be a bad idea, since you’ll reuse these circuits and lot but will need to change the values from lab to lab.
Go-kart circuit from lab 2 is reused in lab 3 — make sure you have a working totem pole, or else that will eat unnecessarily into lab 3 time.
Start on the labs early! and ask for help. Even if it seems like a dumb circuit that should just work, if you’re stuck, asking an experienced circuiteer for help will work wonders and you’ll learn a ton about the circuit too, including all the individual parts which you’ll need to know to help anyone else debug and which you wouldn’t pay attention to if you simply breezed through to a working circuit.
your 74HC wants 5V, not 12V!
connect ALL your grounds.
==== misc from this week: lamp ballast:
to find the resonant frequency, you can try to calc by f = 1 / (2*pi*sqrt(L * C)) = (somewhere in 30 to 40 kHz) and measuring the exact L that you actually wound. alternatively, run the FETs on the totem pole (Vdd) at 12v (Vcc for the IR2125’s is 12V and pulled via a wire from the control circuitry, which you breadboarded on a separate board instead of protoboarded straight on the totem pole board, right?) and adjust the frequency (via pot on 555 or whatever you are using to generate square wave being fed into 311 comparator), sweeping the 30 to 40 kHz range until you found where your power supply is supplying the most current. For me, I found the current peaked at 0.38A at 12v at ~32 kHz (and diminishes to either side), while my calculated resonant frequency was closer to 35kHz. This was the magic sauce that led to my fluorescent bulb striking, yay!
also, you want to ground the ERR pins on the IR2125 / totem with jumpers if you want the 2125s to work. The may work without pulling to ground explicitly, but best not even have to worry about it.