[Appearance] Add Home card roundness, border and background controls #87
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Product intent
Let users tune how prominent BookWave's Home cards feel without changing their content hierarchy: choose card corner roundness and independently decide whether the card's decorative border and background/tint are shown.
This issue is the design/implementation staging area for these card appearance controls and should stay coordinated with #48 and the finished-book indicator issue created alongside it.
Current evidence
Reviewed current
mainatca080a875f95e7e50a3944e1810cf9c76194c167.The shared glass card currently has hard-coded chrome:
GlassDefaults.CardCornerRadius = 12.dp;Modifier.cardGlass()always draws a 1 dpoutlineVariantborder;cardGlassTintEnabled;AppearanceRepository;GlassCard, while other surfaces also reuse it.#48 already proposes making Appearance a clearer live preview tool. This issue is narrower: define and persist the card-shape/chrome preferences themselves.
Proposed controls
1. Card roundness
Add a user-facing control for Home card corner roundness.
Preferred interaction: a slider or small named scale with a live preview, rather than a long list of arbitrary dp numbers.
Candidate scale to prototype:
Implementation may store a bounded numeric value or a stable enum; the UI should use understandable labels and keep the current 12 dp look as the default/migration value.
2. Show card border
Add an independent Card border switch.
3. Show card background
Add an independent Card background switch.
This needs a precise product definition before implementation because the current glass system has both blur and tint/fallback behavior.
Recommended meaning:
Do not silently make “background off” another name for “card tint off” unless rendered investigation proves those concepts are indistinguishable to users. The existing Card tint preference should either remain a separate advanced control or be deliberately reconciled/migrated as part of this issue.
Scope decision to stage
The request is specifically for Home-screen cards. Start with Home as the product scope and design the preference model so it can be safely reused by other card families later.
Before implementation, inventory which
GlassCarduses are truly content cards versus settings groups/chrome. Do not globally square/strip everyGlassCardmerely because they share a primitive.Recommended architecture:
Live preview
Coordinate with #48's proposed Appearance preview. These controls are hard to judge from labels alone.
Preview should show an actual BookWave-style book card and update live for:
Avoid a fake device frame.
Interaction with semantic states
Decorative preferences must not erase state.
In particular:
Storage / migration
cardGlassTintEnabledpreference explicitly and test migration/default behavior.Acceptance criteria
Staging decisions / open questions
GlassCard.Related completion-state staging: #86. Card chrome preferences must not hide or replace the semantic finished-book indicator.