Accessible Smartphone Concept for People Who Are Blind

Quick Overview

A product design case on creating a smartphone for people who are blind. It tests choosing a user segment, rethinking touch-based input and output, prioritizing features that support independent everyday use, and defining success metrics and risks for an accessible device.

Accessible Smartphone Concept for People Who Are Blind

Company: Google

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Design a mobile phone for people who are blind. Decide which blind users you are designing for and what they need from a phone, choose the capabilities the first version launches with, and explain how you would measure whether it truly works for them. ```hint Rethink input and output first A touchscreen assumes the user can see where to tap and read what appears. Decide how a blind user will find, hear or feel information and act on it, then check which everyday tasks that choice makes easy or hard. ``` ### Clarifying Questions - Is this a dedicated phone that Google would build and sell, or an experience that could run on Android phones people already own? - Does "blind" cover only people with no usable sight, or also people with low vision who still rely on some sight? - Should the design target people who are already fluent with screen readers and braille, or people who lost their sight recently and are new to assistive technology? - Is there a price target, or can this be a premium device? ### What a Strong Answer Covers - A segmentation of blind users (for example by when they lost their sight, age, and fluency with screen readers and braille) with a reasoned choice of whom to design for first. - Pain points across a whole day of phone use, not only calls: knowing where you are on the screen, recovering when stuck, reading printed text, getting around, and privacy in public. - An input and output design (voice, touch gestures, haptics, physical controls, braille) suited to the chosen users, and a focused, prioritized first version. - The choice between new hardware and software for existing phones, with its trade-offs for reach and price. - Success metrics centered on completing tasks without sighted help, with guardrails for accidental actions and misreadings, plus risks such as AI errors and camera privacy. ### Follow-up Questions - The phone reads a medication label aloud using the camera and an AI model. How do you design for the case where that reading is wrong? - How would you involve blind people in research and testing, and what can sighted testers wearing blindfolds not tell you? - If version one could include only one capability beyond calls and messages, which would you choose and why?

Overview: A product design case on creating a smartphone for people who are blind. It tests choosing a user segment, rethinking touch-based input and output, prioritizing features that support independent everyday use, and defining success metrics and risks for an accessible device.

Google logo
Google
Aug 2, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

Design a mobile phone for people who are blind. Decide which blind users you are designing for and what they need from a phone, choose the capabilities the first version launches with, and explain how you would measure whether it truly works for them.

Clarifying Questions Guidance

  • Is this a dedicated phone that Google would build and sell, or an experience that could run on Android phones people already own?
  • Does "blind" cover only people with no usable sight, or also people with low vision who still rely on some sight?
  • Should the design target people who are already fluent with screen readers and braille, or people who lost their sight recently and are new to assistive technology?
  • Is there a price target, or can this be a premium device?

What a Strong Answer Covers Guidance

  • A segmentation of blind users (for example by when they lost their sight, age, and fluency with screen readers and braille) with a reasoned choice of whom to design for first.
  • Pain points across a whole day of phone use, not only calls: knowing where you are on the screen, recovering when stuck, reading printed text, getting around, and privacy in public.
  • An input and output design (voice, touch gestures, haptics, physical controls, braille) suited to the chosen users, and a focused, prioritized first version.
  • The choice between new hardware and software for existing phones, with its trade-offs for reach and price.
  • Success metrics centered on completing tasks without sighted help, with guardrails for accidental actions and misreadings, plus risks such as AI errors and camera privacy.

Follow-up Questions Guidance

  • The phone reads a medication label aloud using the camera and an AI model. How do you design for the case where that reading is wrong?
  • How would you involve blind people in research and testing, and what can sighted testers wearing blindfolds not tell you?
  • If version one could include only one capability beyond calls and messages, which would you choose and why?