Placeholder vector artwork behind replaceable resource names #15

New Issue

Closed

opened 2026-08-18 03:33:27 -05:00 by null · 0 comments

null commented

2026-08-18 03:33:27 -05:00

Owner

Every screen in this batch has a slot for artwork and none of it exists. PRODUCT_PLAN.md §42 anticipates exactly this and gives the instruction: "If custom artwork cannot be produced immediately, create polished placeholder vector assets and keep them behind replaceable resource names."

What is needed (§42): onboarding illustrations of overlapping circular forms, an empty state, a learning state of points converging into a pattern, a privacy shield motif, and calendar markers for confirmed period, predicted period, fertile window and estimated ovulation.

Hard constraints, and they are the reason this is an issue rather than a chore: no blood drops, tampons, pads, uterus imagery, gender symbols or anatomical graphics. Abstract circular forms and soft curves only. VectorDrawable or Compose paths, never raster.

Calendar markers must remain distinguishable without colour — §26 and §43 both require it, and it is what makes the calendar readable to a colourblind user and in a greyscale screenshot.

Note the deliberate contrast with docs/data/img/ (#8): those three marks must not be faked, because a placeholder that looks finished outlives the issue that would replace it and nobody files a ticket against an image that appears done. In-app assets are different — §42 asks for them, and a replaceable resource name is the mechanism that keeps them replaceable.

Verify: every artwork slot in the Batch 03 screens renders a vector asset, find app core -name '*.png' -o -name '*.jpg' returns nothing under src/, and the four calendar markers are distinguishable in a greyscale screenshot.

Every screen in this batch has a slot for artwork and none of it exists. PRODUCT_PLAN.md §42 anticipates exactly this and gives the instruction: *"If custom artwork cannot be produced immediately, create polished placeholder vector assets and keep them behind replaceable resource names."* What is needed (§42): onboarding illustrations of overlapping circular forms, an empty state, a learning state of points converging into a pattern, a privacy shield motif, and calendar markers for confirmed period, predicted period, fertile window and estimated ovulation. Hard constraints, and they are the reason this is an issue rather than a chore: **no blood drops, tampons, pads, uterus imagery, gender symbols or anatomical graphics.** Abstract circular forms and soft curves only. VectorDrawable or Compose paths, never raster. Calendar markers must remain distinguishable **without colour** — §26 and §43 both require it, and it is what makes the calendar readable to a colourblind user and in a greyscale screenshot. Note the deliberate contrast with `docs/data/img/` (#8): those three marks must **not** be faked, because a placeholder that looks finished outlives the issue that would replace it and nobody files a ticket against an image that appears done. In-app assets are different — §42 asks for them, and a replaceable resource name is the mechanism that keeps them replaceable. Verify: every artwork slot in the Batch 03 screens renders a vector asset, `find app core -name '*.png' -o -name '*.jpg'` returns nothing under `src/`, and the four calendar markers are distinguishable in a greyscale screenshot.