UX: Add what-matters-now state cues #25

Closed
opened 2026-04-04 05:35:48 +00:00 by Brouie · 5 comments
Brouie commented 2026-04-04 05:35:48 +00:00 (Migrated from gitlab.com)

page should adapt to game state. during active sale: highlight timer + buy panel. sale ended: highlight redeem + prizes. guard active: show guard countdown. revenge available: surface it prominently. reduce noise by de-emphasizing sections that dont apply to the current state.

page should adapt to game state. during active sale: highlight timer + buy panel. sale ended: highlight redeem + prizes. guard active: show guard countdown. revenge available: surface it prominently. reduce noise by de-emphasizing sections that dont apply to the current state.
Brouie commented 2026-04-06 06:52:50 +00:00 (Migrated from gitlab.com)

reviewed on 254999d. the page doesn't adapt to game state. sale ended but the layout is identical to what you'd see during an active sale -- onchain data, buy panel (disabled), warbow section, podiums, all in the same order. during active sale: timer + buy + battle feed should dominate. sale ended: redeem + prizes + final standings should dominate. guard active: guard countdown should be prominent. revenge available: surface it at the top. the current page treats all states the same. screenshot attached.

reviewed on 254999d. the page doesn't adapt to game state. sale ended but the layout is identical to what you'd see during an active sale -- onchain data, buy panel (disabled), warbow section, podiums, all in the same order. during active sale: timer + buy + battle feed should dominate. sale ended: redeem + prizes + final standings should dominate. guard active: guard countdown should be prominent. revenge available: surface it at the top. the current page treats all states the same. screenshot attached.
Brouie commented 2026-04-06 07:00:35 +00:00 (Migrated from gitlab.com)

image.png{width=849 height=449}

![image.png](/uploads/7ffde5d4717af35231968b509ebcab7e/image.png){width=849 height=449}
PlasticDigits commented 2026-04-09 04:53:14 +00:00 (Migrated from gitlab.com)

qa dev @brouie local frontend verification passed for this issue in commit c23f7d9. Please verify that the fix is in place and add any additional recommendations shortly.

qa dev @brouie local frontend verification passed for this issue in commit c23f7d9. Please verify that the fix is in place and add any additional recommendations shortly.
Brouie commented 2026-04-09 06:36:41 +00:00 (Migrated from gitlab.com)

Verified on 4e4ec94 with local Anvil stack (live data). Fix is in place. Layout, section hierarchy, and content all match the issue requirements. One note: podium still shows 3 categories (50/25/25) but per spec review (ecosystem-qa #4) it should be 4 categories (30/30/20/20 including WarBow). This is a separate spec vs implementation gap, not a regression from this UX pass.

Verified on 4e4ec94 with local Anvil stack (live data). Fix is in place. Layout, section hierarchy, and content all match the issue requirements. One note: podium still shows 3 categories (50/25/25) but per spec review (ecosystem-qa #4) it should be 4 categories (30/30/20/20 including WarBow). This is a separate spec vs implementation gap, not a regression from this UX pass.
Brouie (Migrated from gitlab.com) closed this issue 2026-04-09 06:39:36 +00:00
Brouie commented 2026-05-15 02:40:25 +00:00 (Migrated from gitlab.com)

mentioned in issue #204

mentioned in issue #204
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
code/yieldomega#25
No description provided.