Work / Plate 05 of 06

Android 16 KB fix map

A reference people land on from a search should answer the question in the first screen, show its working, and say what it deliberately does not claim.

Year: 2026
Status: Own product
Brief: Programmatic data site with free tools and a paid kit
Medium: Python generator, static HTML, Cloudflare Pages
Mobile speed: Lighthouse 98, 385 KB
Shown at: android-16kb-fixmap.pages.dev
Palette: #0F1113#ECEBE6#7BD12E

Open the live product Live product, redesigned.

Android 16 KB fix map, first screen at 1440 pixels wide

Plate 05. Android 16 KB fix map, first screen at 1440 pixelsWall painted in the work's own #0F1113

What was built

Product, data method and sign-off: Angel. Measurement scripts, page generator, copy and QA: AI-agent pipeline; the page says so on its face.

A data site that answers a Play Console warning in the first screen. The design job: make the measurement itself the visual, with each library drawn as the 4 KB or 16 KB pages it really occupies, then a clear step from the free checker to the paid kit.

A generator that downloads the published artifacts of 80 Android native libraries and measures the ELF alignment of each .so file
80 library pages and an index, built statically from the dataset
A deadlines section at the top (targetSdk 36, Billing Library 7, the 16 KB page-size rule), with a countdown and a page per exact Play warning
A free dependency-free checker script and a paste-your-dependencies page
A paid kit with hosted checkout, and a double opt-in watch form that stores only an email, the library ids and the consent wording
A 'Deliberately not claimed' section listing what was not measured

Stack Python generator, static HTML, Cloudflare Pages, a small Cloudflare Pages Function and D1 for the watch form

Decisions, with the reasons.

Data

The headline number is a count you can check

The title says how many libraries were measured (80). Under the Play warnings and deadlines, the table is split by outcome in the order a developer needs: 63 fixed by upgrading, 11 with no aligned release yet, 4 where the native code was removed, 2 relocated to another artifact. Each row names the exact artifact and the version to move to.

80 libraries measured

Fixed: upgrade to an aligned version63
No aligned release found11
Native code removed in newer versions4
Relocated to another artifact2

Counts from the live page, 2026-10-06. Every row on the site names the exact artifact and version.

Approach

A section for what is not claimed

Four items the data does not cover (a private-Maven SDK, an editor-bundled engine, a media decoder set, React Native app builds) are listed on the page with the reason. Limits stay visible next to the paid offer instead of being buried. The footer says the pages were generated by a script, AI-assisted, with numbers measured and not copied from release notes.

Rejectedpadding the count with libraries that were not downloaded and measured.

Interaction

From free answer to paid kit

The free tier is the whole table, the in-browser checker and the checker script. A Free vs. the Kit comparison sits above the table: the kit ($12) adds the full dataset as JSON and every raw measurement, a fix guide and updated downloads, with a 14-day refund stated next to it. A watch box asks for an email and an explicit consent tick for status alerts.

First screen on a phone: the warning and the deadlines

Fixed libraries: artifact and target version per row

How it was started Built from a measured dataset, not hand-written pages. The generator is a single script, so adding a library is a data change and every page, sitemap entry and table stays consistent.

Figures, captured live.

Screenshots I took from the running preview at 1440 and 390 pixels wide. They are not mock-ups.

Android 16 KB fix map: First screen: warning, deadlines, drop-in checker — First screen: warning, deadlines, drop-in checker

Android 16 KB fix map: One real library, unrolled into 16 KB pages — One real library, unrolled into 16 KB pages

Android 16 KB fix map: Same code, rebuilt on the grid — Same code, rebuilt on the grid

Android 16 KB fix map: All 2,065 measured versions, one square each — All 2,065 measured versions, one square each

Android 16 KB fix map at 390 pixels wide

Measured, not claimed.

98Performance

100Accessibility

100Best practices

100SEO

Largest contentful paint: 2.3 s
Layout shift: 0
Blocking time: 60 ms
Page weight: 385 KB
Fonts: schibsted-grotesk-latin-wght-normal.woff2 46 KB
ibm-plex-mono-latin-400-normal.woff2 15 KB

Lighthouse 12.8.2, simulated mobile, one run against android-16kb-fixmap.pages.dev/ on 2026-10-06. Lab data, not field data. Re-run before quoting these elsewhere.

Honest limits.

No traffic or ranking claims: no Search Console data yet, so none are made.
The first screen and the figures are code-drawn, not photography; the hero image is labelled as a generated illustration on the page.

Next plate

Add audio to videoFree browser tool that adds an audio track to a video, or turns an image and audio into a video

Want a redesign demo of your own site?

Free and private. You only pay if you want the full build.

Try the Redesign Lab

RequestYour site and consent
AuditBy email, straight away
Private demoAbout five days
Optional buildOnly on payment
Case studyOnly with your yes