Skip to content

Lock: digits-only keypad over an even scrim (revision 2) - #85

Merged
henrikklee merged 8 commits into
mainfrom
lock-keypad-rev2
Nov 19, 2026
Merged

henrikklee merged 8 commits into
mainfrom
lock-keypad-rev2

Conversation

@henrikklee

@henrikklee henrikklee commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Stacked on #82 (status icons on the lock), which is on #81.

The shell spec's lock-screen revision 2 as updated (lock-pin-rev2-*, including the landscape reference). Behaviour is unchanged.

  • Keys are bare digits: 26 px on an iPad and 24 on a phone, in full tap cells (80 × 56 on an iPad, never under 44 tall) with nothing drawn around them. A faint square shows only while pressed; backspace gets the same treatment.
  • Scale: clock 96 (90 in landscape), date 16, and PIN slots as 12 px squares with 14 between them. The block stays centred, and the keypad is a compact cluster. In landscape the clock and keypad sit closer together, as in the reference.
  • Background: one even scrim, using the theme's lock.scrim, whose default is now 70 %. A soft dark shadow sits under the clock, date, slots and keypad: the background colour at 80 %, about 8 px of blur, 1 px down. Empty slots get a faint dark fill behind their outline. No gradient, as the spec says.

Tested in the Orchard simulator: live on the iPad in landscape, plus earlier off-screen renders across all 23 bundled themes. Not yet on a real tablet. Tests pass apart from the image-picker tests that need Linux.

The shell spec's lock-screen revision 2: the keypad loses its boxes. Each
key is a bare digit (34 px on an iPad, 28 on a phone) in a full tap cell,
with a faint square behind it only while pressed; backspace the same.
Empty PIN slots are outlined in the lock's secondary text colour.

The flat scrim becomes a gradient of the theme background, light behind
the clock (the theme's lock.scrim) and dark behind the keypad (60, 90,
95 %): down the screen in portrait, across it towards the keypad's side in
landscape (mirrored right to left). It keeps bare digits readable on a
bright wallpaper. Layout and behaviour are unchanged.

Assisted-by: LLM
On a dark theme the gradient's colour is the background taken almost to
black (as the design's #0b0c12 is Tokyo Night's): it darkens the
wallpaper and keeps its colours, where the background itself turned warm
wallpapers a muddy grey-purple. A light theme keeps its background.

Assisted-by: LLM
From the spec's update: digits 26 (24 on a phone), cells 80 x 56 with 20
across and 10 down, clock 96 (90 in landscape), date 16, slots 12 with 14
between: a compact block centred on the screen. A phone scales the same
way and keeps cells at least 44 points tall.

Assisted-by: LLM
The gradient eases (smoothstep) over the whole screen from 12 % by the
clock to 55 % by the keypad's far edge: the wallpaper stays clear, with
just enough shade under the digits, and no edge to see.

Assisted-by: LLM
The spec's revision 2 as updated: no gradient (tried and rejected), one
even scrim, the theme's lock.scrim now at 70 % by default; a soft dark
shadow under the clock, date, slots and keypad (the background at 80 %,
about 8 px of blur, 1 px down); empty PIN slots with a faint dark fill
behind their outline. In landscape the clock and keypad sit closer, as in
the new landscape reference.

Assisted-by: LLM
At 70 % the theme background itself (Tokyo Night's navy) turned warm
wallpapers a muddy grey-purple. On a dark theme the scrim is now that
colour taken almost to black, at the same strength: the wallpaper only
gets darker. A light theme keeps its background.

Assisted-by: LLM
@henrikklee henrikklee changed the title Lock: digits-only keypad over a dark gradient (revision 2) Lock: digits-only keypad over an even scrim (revision 2) Nov 19, 2026
@henrikklee
henrikklee changed the base branch from status-cluster to main November 19, 2026 21:09
@henrikklee
henrikklee merged commit 7185656 into main Nov 19, 2026
9 checks passed
@henrikklee
henrikklee deleted the lock-keypad-rev2 branch November 19, 2026 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant