UX: Improve buy panel emotional clarity #21

New issue

Closed

opened 2026-04-04 05:34:42 +00:00 by Brouie · 4 comments

Brouie commented

2026-04-04 05:34:42 +00:00

(Migrated from gitlab.com)

buy panel should make it immediately clear what you get -- charms earned, timer impact, battle points, podium position change. right now it's a form with technical fields. needs emotional payoff preview before you commit.

Brouie commented

2026-04-06 06:51:59 +00:00

(Migrated from gitlab.com)

reviewed on 254999d. the buy panel says 'Sale is not active (not started or already ended)' when sale has ended. when active, it shows technical fields: charmWad, gross spend formula, referral bonuses as text. a player about to buy needs emotional clarity: how many charms they'll get, what podium positions they could affect, how much time they'll add to the countdown, what their battle points will become. the current form feels like filling out a contract call, not making an exciting game move. screenshot attached.

reviewed on 254999d. the buy panel says 'Sale is not active (not started or already ended)' when sale has ended. when active, it shows technical fields: charmWad, gross spend formula, referral bonuses as text. a player about to buy needs emotional clarity: how many charms they'll get, what podium positions they could affect, how much time they'll add to the countdown, what their battle points will become. the current form feels like filling out a contract call, not making an exciting game move. screenshot attached.

Brouie commented

2026-04-06 07:08:03 +00:00

(Migrated from gitlab.com)

{width=818 height=600}

![image.png](/uploads/2b90c49fd76b40b004f24cf9ac10d260/image.png){width=818 height=600}

PlasticDigits commented

2026-04-09 04:53:10 +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:36 +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:28 +00:00

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#21

No description provided.

Rows
Columns