01 / Problem
Present several offers without making the store feel chaotic.
Players need to compare reward amounts and prices quickly while still recognizing special value and understanding how to leave.
Storefront / Monetization / Choice
Coin Store UI
A mobile storefront study that organizes purchase tiers, emphasizes value, and keeps the player’s current balance visible.
- Focus
- Storefront UI, offer comparison, component repetition
- Format
- Static design study
- Status
- Concept
The design at a glance
Make purchase choices easy to compare.
Repeated rows establish a consistent reading pattern: reward image, coin amount, and price. A ribbon calls out a featured offer, while the balance and free-coin action remain visible.
This study demonstrates interface composition. It does not claim conversion results, shipped transactions, or user research.
02 / Design intent
Create a repeatable offer pattern.
Each tier uses the same structure so the eye can compare vertically, with larger coin bundles represented by increasingly substantial containers.
03 / Key decisions
Keep value and action together.
- Coin quantity and price share each row.
- The featured-value ribbon breaks the pattern intentionally.
- A close control stays in the upper-right corner.
- The current balance remains anchored at the bottom.
04 / Interaction & usability
Reduce uncertainty before purchase.
A production flow should identify currency, explain any rewarded-video action, confirm purchases, and support cancellation, success, error, and insufficient-funds states.
05 / Tools & skills
What this demonstrates
Storefront composition, component consistency, visual hierarchy, pricing presentation, callout styling, touch targets, and game-economy interface thinking.
06 / What I’d improve next
Make the offer logic more transparent.
- Add explicit currency formatting and per-unit value.
- Clarify the free-coins action and its consequence.
- Strengthen text consistency and reduce decorative shadowing.
- Prototype confirmation and recovery states.
Thinking as a product system
I would turn the repeated offer row into a reusable component with inventory, localization, pricing, accessibility, and transaction states defined before implementation.