QCon 2018 – Smart Speakers Designing for the Human

Posted on by
Reply

Title: Designing for the Human
Speaker: Charles Berg (from Google Home)

See the table of contents for more blog posts from the conference.

Over half the audience has smart speakers at home (Echo, Alexa, etc)

Most common uses of smart speakers

  • Communication (calls, texts)
  • IOT (turn on lights, fans)
  • Clock (alarms/timers)
  • Music

History

  • Encourages checking out of the environment. Even a notification gets you back into your phone
  • We focus on features and apps, but not the reason why users is doing something. App first human second mindset is a problem.

Smart speakers

  • Unlike smart phones, they are fixed in space. Direct voice to it.
  • Place it near where plan to use it.
  • That usage leads to context.

Agile

  • Ask questions
  • Do research before had design
  • Storyboards

Calling use case

  • Call dentist – should be seemless
  • Call Walgreens – which one?
  • Hands free calling for friends is frequent

Process

  • Understand context.
  • In a medium to large company, there is a lot of research already going on.
  • Find archived research. Don’t need to do from scratch.
  • Interview – start internal to team, then friends/family
  • Quickly need to expand interview to be more broad.
  • Pitch teammates on ideas based on research
  • Identify lead designer. Then identify themes (summary of research), brainstorm and create user journey map.
  • Physical user testing. Made two rooms with a mattress instead of just talking about it.

Smart speakers and dialog

  • There is a smart speaker style guide.
  • Develop variations
  • Test with actual people; see variation

My take

This was fun. It was a good mix of smart speakers and user focused design. I would have liked for more of the examples to be about speakers (vs an example about pretend stock quotes). Reading the abstract, I wasn’t sure how much to expect of each type of information. I don’t know if it was reasonable to expect, but I was expecting more on the smart speakers. And then right after I typed this, there was more on the speakers. Good. So maybe it wasn’t the amount of information, but the distribution of it. And the QA definitely went back to speakers.

 

QCon 2018 – Rethinking HCI with Neural Interfaces

Posted on by
Reply

Title: Rethinking HCI with Neural Interfaces
Speaker: Adam Berenzweig @madadam

See the table of contents for more blog posts from the conference.

Minority Report analysis

  • why need gloves to interface
  • ergonomics – tiring to hold arm up

History of UI Paradigm Shifts

  • Command line – we still use the command line; just not exclusively
  • mouse, graphics – original Apple. Design innovation; not just tech
  • minesweeper and solitaire built in so could learn how to use the mouse – right click for minesweeper and click/drag for solitarire
  • MIT wearable computing in 1993 paved way for Google Glass. [but successful]
  • Joysticks, gloves, body (Kinect), eye tracking, VR/AR headsets
  • Had audience raise hand if wearing a computer. Not many Apple watch people in the room
  • Future: tech is always there. It knows about the world around you and is always ready

Book recommendation: Rainbow’s End – an old man gets rejuvenated (or something) and comes back younger needing to learn new tech

Intro to Neural Interfaces

  • Interfaces devices to translate muscle movement into actions
  • Human input/output has high bandwidth compared to typing or the like. We think faster than we can relay information. Output constrained.
  • Myo – For amputee, arm where have electrode on arm that controls arm.
  • Neural interfaces have information would have sent to muscle or physical controller
  • Lots of stuff happens in the brain, but you don’t want all of it. You want the intentional part without having to filter out everything else. The motor cortex controls muscles so represents voluntarily control. Also don’t have to plan electrodes on brain.

Examples

  • Touch type without keyboard presence [not very practical as it is hard to touch type without seeing keys]
  • Mirrors intention of moving muscles even if physical attempt is blocked
  • VR/AR – more immersive experience

Designing for Neural Interfaces

  • Want to maximize control/minimize effort
  • Cognitive limits – what can people learn/retain
  • Mouse is two degrees of freedom, laser pointer is three. There is also six where control in space. Human body has ore than six degrees of freedom. Are humans capable of controlling an octopus
  • How efficient is the input. Compared to existing control devices
  • It is possible to control three cursors at once, but it is exhausting. Not a good design
  • Different people find different things intuitive. Which way is up?
  • Don’t translate existing UIs. Can evolve over time.

My take

Fun! Great mix of pictures, videos and concepts. I learned a lot. Would be interesting to see this vs the privacy/ethics track. Imagining what data it could have reading your mind/muscles.

QCon 2018 – Data, GDPR & Privacy

Posted on by
Reply

Title: Data, GDPR & Privacy – Doing it right without losing it all
Speaker: Amie Durr

See the table of contents for more blog posts from the conference.

Goals: send right message to right person at right time using right channel (ex: email, text, etc)

One company handles 25% of all non-spam email traffic

Confidence

  • We don’t trust brands with personal information. 2/3  overall. Nobody in room.
  • Employees at GDPR  compliant companies also don’t believe their company is

Recent thefts

  • Ticketfly – emails and hashed passwords.   Shut down their website
  • Panera – email, name, phone, city, last 4 digits of credit card number
  • MyHeritage – email and hashed passwords
  • Myfitnesspal – name, weight, etc

Need to consider

  • What do you store?
  • For how ong do you store it?

Data and privacy regulations

  • CASL
  • CAN-SPAM
  • Privacy Shield – for data leaving Europe
  • GDPR – EU
  • Future: Germany, Australlia, South America
  • Not about specific regulations. Need to care about data an privacy. Part of   Brand. Customers will leave

Supply for data scientists far exceeds supply

Build trust without stiffling innovation

  • accountability – what do with data, who responsible, continuing to focus on data perception,  audit/clean data, make easy to see what data  have and how opt out/delete
  • privacy by design – innovate without doing harm, don’t want to get hacked, be user centric, move data to invididual so no storing, what is actually PII vs what feels like PII. Anonymize both

Remember user data. If the user types it in, could be anything in here

What they did

  • dropped log storage to 30 days. Have 30 days to comply with requests to delete data. So  handled by design for log files
  • hash email recipients
  • Remove unused tracking data
  • Communicated with customers
  • Kept anonymized PII data, support inquiries, etc
  • some customers feel 30 days is too long so looking at going beyond law

Can delete parts of data vs everything (ex:: stack overflow)

brand and pr vs actually keeping user safe [like what happened with accessibility and section 508]

My take

Good talk. I liked the level of detail and concrete examples. I would have liked a refresher of GDPR. But there was enough to tell me what to google. That helped with what didn’t know (or forgot).