Onboarding artwork as full-bleed landscape masters #39
Labels
No Label
P0
P1
P2
release-blocker
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: null/Privacy-Period-Tracker#39
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The onboarding illustrations read as stickers rather than as artwork, and the fix is not a code change.
What is true now
Measured on the Pixel 6 profile, 411 × 914 dp:
There is no high-resolution master.
docs/design/dist/Light/andDark/hold 365–553 × 481–488 px files — the same pixels as the shippedcore/designsystem/src/main/res/drawable*/art_*.webpat 480 px tall. Rendering at 280 dp needs 735 px at 2.625×, 840 px at 3× and 1120 px at 4×, so enlarging what exists means a 1.5–2.3× upscale and visible softness. Even today's 160 dp already upscales 1.3× on xxxhdpi.The background cannot be removed programmatically. It is a gradient landscape, not a flat field: sampled edge pixels on
art_welcome.webprun(233,231,243),(227,212,231)and(243,236,241). No flood fill or chroma key applies, and no background-removal tool is installed on this machine.The generator already produces what is needed:
docs/design/brand/icon.webpanddocs/design/dist/splash.webpare 1254 × 1254 with real alpha, while the onboarding set arrived at 365 × 488 with none.The decision
Keep the scene — the sunrise landscape is the brand, not decoration — and present it full-bleed, fading into the app background, at roughly 30% of screen height.
What to produce
Eight illustrations × two themes, replacing the current set, delivered into
docs/design/dist/Light/andDark/under the existing stem names sodist/README.md's mapping table stays true.docs/design/dist/README.md, so a theme switch never moves the layout.Traps
Each of these was a correction during an earlier review and each is easy to reintroduce by regenerating carelessly.
docs/design/dist/README.mdrecords all four with reasons:Heading(...); baked text prints twice, cannot be translated, cannot scale with the user's font size, and is invisible to TalkBack.LearningIllustrationis also the Insights empty state, where a number means nothing, and baked numbers freeze a running order this flow has already changed once.07_Forecastnames no fields. No "fertile window", no "ovulation", no confidence value — the live forecast beside it declines to estimate fertility on a first run, and art that contradicts it is the one thing §11 and §18 exist to prevent.BRAND_GUIDE.md§14 specifies.Brand constraints: start from
BRAND_GUIDE.md§22's master prompt, with §15 (semi-3D depth, soft glow, no harsh shadows), §16 (rounded geometry) and §23 (dusty rose not bubblegum, plum not electric violet, botanicals elegant and secondary). §42's forbidden list applies to every in-app illustration perdocs/design/README.md— no blood drops, tampons, pads, uterus imagery, gender symbols or anatomy, because this app is opened in public.Why filed and not fixed
An agent cannot draw these, and must not fake them — the same reason the three branding marks waited for a person. The app-side work is separate and can land first.
Verify: sixteen files exist in
docs/design/dist/Light/andDark/under the existing stem names, each at least 2048 px wide in 3:2, each light/dark pair identical in dimensions, and none carrying text, a step number, or a named forecast field.Shipped in
b74bc4b. Sixteen files at 3:2, composed natively wide — verified by measuring edge detail across each image and testing for the step change a pasted rectangle leaves; none has one, against 15 of 16 in the first attempt. Also caught and replaced a byte-identical duplicate. Note the follow-up in #44: dark 01 is a forecast scene, which this issue's uniqueness check could not catch.