TypePass

An iOS app for trying a display typeface and checking whether it stays readable: contrast at each size, letters that look alike, and how large to set it on a sign.

Timeline
2 weeks
Team
Independent
Role
Product Designer
Focus
Mobile Design
Interaction Design
Accessibility
Problem Research Reframe Process Testing Components Design Reflections
Problem

A specimen shows the letters, not whether they read

Pitching a typeface to a client on site, a PDF specimen shows the letters. It can't tell you if people can read them.

Text and Display sit apart

Lapture's Display cut is drawn for large sizes and its Text cut for small text. Specimens list them as separate styles, never side by side.

The guidance lives elsewhere

Contrast, sign sizes and the letter pairs readers confuse all have published guidance. None of it is in the specimen.

Research

Six specimens and apps, and what they leave out

I compared Lapture's foundry page and its Adobe Fonts listing with four apps designers already use for type: Typography Insight, WhatTheFont, Adobe Capture and Fontstand.

FeatureTypography
Insight
JAF
Lapture page
Adobe
Fonts
What
TheFont
Adobe
Capture
Fontstand
(iPad)
TypePass
Works on a phoneHasNot confirmedNot confirmedHasHasLacksHas
Type your own textNot confirmedLacksHasLacksLacksNot confirmedHas
Close look at letter anatomyHasLacksLacksLacksLacksLacksHas
Text and Display comparedNot confirmedLacksNot confirmedLacksLacksLacksHas
has lacks? not confirmed

Tracing one task

Naming the font on Gmail's Compose button from a photo in WhatTheFont: the camera and its dashed boxes made the next step obvious, but nothing said which box to tap, and the top matches looked nothing like Gmail's sans.

Takeaway

Each covers a piece. Typography Insight looks closely at letters, Adobe Fonts lets you type your own text, and none compares Text and Display. TypePass puts them in one app on a phone, then adds the accessibility checks.

Sources: Just Another Foundry, Lapture; Adobe Fonts, JAF Lapture; App Store listings for Typography Insight, WhatTheFont, Adobe Capture and Fontstand for iPad. Checked October 27, 2026.

Reframe

One strong idea instead of three

My first concept tried to cover all three opportunities: Lapture on the client's storefront through the camera, three checks, and a link to send the client mock-ups. It did a little of everything and nothing well. So I kept the one idea I hadn't seen typeface apps take on: whether the type is readable.

The first concept in low fidelity: eleven screens across Home, Chart, Check and In Use tabs, from starting a project with the client's name to three checks (Sign Distance, Old but Readable, Details), the name on a photo of the storefront, and a link of mock-ups sent to the client

From

"Pitching a typeface to a client, on site."

To

"A specimen app that tells you if your typeface passes."

Process

Set it up in Library, check it in Accessibility

The flow took seven versions to get here. In the final one, you pick Lapture in Library and set its cut, weight and preview text, and Accessibility checks that same setup.

The app's flow: Library leads to search and filter and to the Lapture page, with Specimen, Characters, character detail and Credits; Accessibility leads to Size and contrast with its colour sheet, Look-alikes and Signage

Saving was cut

An earlier version saved styles for Accessibility to check. Nothing else read the saved list, so Accessibility now checks what is set on the Lapture page.

Signage is always on

Sign distance is the one opportunity I kept from the first concept, so it isn't hidden behind a switch.

Five ways to pick a weight, then a sixth

I tried the weight picker as circles, a stepped slider, a list, a dial and a type strip. I kept a sixth: the letters do the comparing and only the pick gets a black circle, the same rule as the tab bar's black pill. One shape instead of five keeps the card quiet next to the specimen.

Six weight pickers on the Lapture page, each with notes: circles, a stepped slider, a weight list, a gauge dial, a type strip with a dot, and the chosen type with one black circle
Each Accessibility card drawn three ways with notes: look-alikes as tiles, ranked bars or overlaid pairs; size and contrast as two cards, one card or sample first; distance as a sentence, two numbers or letters at their ratio

Three versions of each check

Each Accessibility card went through three versions, judged against WCAG and the app's own rules. Look-alikes went from yellow tiles to ranked bars: the tiles showed risk by colour alone, and yellow already meant the live result. Size and contrast became one card, because WCAG's contrast rule depends on the size of the text.

Testing

What testing in pairs changed

I tested the hi-fi prototype with classmates in pairs. Their feedback came down to three things.

Microinteractions

Every tap now gets a response. One spring runs almost everything, so the app feels like one thing, and a bouncier one is kept for things that pop in.

One shape language

Cards, rows and buttons now share one squircle corner, after I worked out what a squircle actually is.

Onboarding

The app used to start by asking for a client's name. Now it opens straight on the Library.

What a squircle actually is: a rounded rectangle, iOS's continuous corner, an icon-style squircle and a true superellipse, each drawn as an open card, a list pill and a square
Components

Everything but Lapture stays in the background

The interface is set in SF Pro on greys. Lapture only appears where you're judging it: the specimens, the characters and the samples.

Yellow only means look here

Paper, surface, ink and one highlighter. Yellow is the only accent, and it always sits under ink: the live result, a selection, a value you set.

A mark must read without the yellow

Anything the app points out is marked like a highlighter on a proof. If a mark doesn't read without the yellow, it is wrong.

Visual identity: SF Pro, with highlighter #FFE56B, surface #E8E8E8, paper #F4F4F4, ink #1C1C1C and line, ink at 48%
Type and colour
The components: the floating tab bar on each tab, back, glass and in-content buttons; filter and view chips, the Display or Text style picker and the weight picker; search, preview text and Library rows; the Library card and the character card; and the Size and contrast, Look-alikes and Signage cards with the Text colour sheet
Components, on the colours they sit on
Design Breakdown

Six moments, from the Library to a sign

Each phone is the working prototype, looping one step.

Open the full prototype

Scroll, filter, then search

Finding a typeface

The Library opens on Lapture in focus. Scroll the stack, filter to Serif, Sans or Other, or search by name.

A weight, your own words, then Text

Setting a style

Pick one of five weights, type your own words, and switch between the Display cut for large sizes and the Text cut for small text. Text only has Regular and Bold, so the weights follow.

One letter, the next, then Black

Every character

The full character set in a grid. Tap one to see it large against its ascender, cap height, x-height, baseline and descender, then step to the next.

Too light, then the nearest pass

Contrast

Change the text or background colour and every size is checked against WCAG as you drag. When a colour fails, the app offers the nearest one that passes.

Look-alikes, then distance and cap height

Look-alikes and signage

Look-alikes ranks the letter pairs readers most often confuse by how much they overlap in this style. Signage turns a viewing distance into a minimum cap height, from the ADA standard.

Credits, and the sources behind the checks

Credits and sources

Credits names Lapture’s designers and foundry, and the sources behind every check.

Reflections

What the checks can't say yet

Look-alikes have no pass mark. Their scores come from overlapping each pair's letter shapes, and there is no agreed cut-off, so pairs are ranked rather than passed or failed.

Back to Work ←