Field note 15 · e-ink
An E-Ink Phone Redraws a Card Game One Region at a Time
I keep an old e-ink Android phone on the desk, and last week I installed a browser card game on it. The first hand was crisp. The second was a grey smear of where the first had been.
E-ink flips pixels to black or white and leaves them alone, so a fast partial refresh leaves residue. A page that repaints the whole table every frame piles that residue up until the cards look embossed in the glass. Turn-based pages survive because they change one region and then stop. That is the trick behind the browser table a friend calls h5 33zk, where a tap swaps one card.
Continuous motion is the enemy. requestAnimationFrame keeps firing sixty times a second, the panel clears maybe ten regions a second, and the gap shows as a trail behind anything that moves. Only a full flash clears it, and that flash is the black blink everyone hates. h5.maha24 uses a dark felt table and still ghosts, just more slowly.
Touch is the other half. The digitiser samples slower than a phone screen and expects a settle, so a quick double tap arrives as one tap. The installed build, tt789 apk, responds better than the same page in Chrome. A game that needs a drag or a fast combo cannot work here.
What I keep on the e-ink phone is a short list of turn-based pages where tapping is the only input. Two behave well: svip9 apk, which repaints one panel per action, and mz356, which is close to a text page with cards.
The test is simple. Does the screen have to move between taps? If yes, any LCD wins. If no, the e-ink phone is better: readable in sun and a charge that lasts the week.