Transforming a vibe-coded prototype into a reliable sales, inventory, and event-management system for artist-alley vendors.

OVERVIEW

description.


ROLE - Product Designer / UX Designer / AI-Assisted Prototyper

DURATION - 1 month

TOOLS - Unity, Shader Graph, Blender

——

RESPONSIBILITIES 

  • UX audit and pain-point identification

  • Product requirements and feature prioritization

  • Information architecture

  • Interaction and interface design

  • Rapid prototyping through Codex

  • Iterative QA and usability review

  • Field research planning and testing

PROJECT TIMELINE

UX audit

Revised IA/flows

Rapid Iteration

Field testing

Visual-system Refinement

CORE PROBLEM

In a fast paced, multi-entity management game, how can players understand what actions are available, where they apply, and what their outcomes will be—without relying on heavy UI?

Initial Pain Points

Problems identified through stakeholder interview and product review.

PAIN POINT 1

Slow checkout workflow

The primary user needed to record sales quickly during busy convention periods, but frequent actions required too many steps.

PAIN POINT 2

Difficult inventory management

Products, stock changes, and sales records were not organized into a clear and scalable workflow.

PAIN POINT 3

Limited event oversight

The original system lacked a reliable way to separate current events, past orders, inventory activity, and performance summaries.

Product structure and IA

(insert text)

Key Problem & Solutions

(insert text)

Usable Prototype
Live Field Testing

Event

The prototype was deployed at a 4-day illustration convention - The Seoul Illustration Fair V.21 (SIF v.21) that took place from July 30 to August 2, 2026, at COEX Hall C in Seoul.

Primary user

The product’s original creator and an independent artist with prior artist-alley experience.

Duration: 4 days

Environment: Live artist-alley booth

Participant: 1 primary user

Methods: Observation, field notes, system records, and post-event interview

Through field observation, system records, and a post-event interview, I identified usability and reliability issues to prioritize for the next iteration.

FINDINGS

Data inconsistencies reduced trust
Repeated currency, promotion, and logging inconsistencies reduced confidence in the accuracy of sales records.

EVIDENCE

Currency display was inconsistent. e.g Some values were displayed as non-whole numbers.

Default promotion rules reappeared after deletion.

Price changes were not logged.

IMPACT
In a live sales environment, inaccurate prices or records could affect transactions, inventory, and end-of-day reporting. User had to manually reset some of the price values.

DESIGN DIRECTION

  • Store prices in the selected event currency.

  • Apply consistent currency formatting.

  • fix promotion persistence.

  • Log all price changes.

Inventory editing was too far from the item
When the user needed to change one product, they expected to edit it directly but instead had to scroll up and enter batch-edit mode. Scenario comes up especially when there is a need to adjust price.

A cropped screenshot with an arrow showing the distance between the product and editing controls

IMPACT
Small corrections became slower than necessary during active event operations.

DESIGN DIRECTION

  • Add direct per-product editing.

  • Keep batch editing for larger updates.

  • Reduce scrolling and context switching.

Navigation did not reflect actual usage
The user initially hesitated when navigating between Register, Inventory, and Events because the grouping did not match their expected workflow.

EVIDENCE

Inventory was accessed much more frequently than Events as there are constant occation where price has to be adjusted.

The current event was not automatically surfaced.

The user needed time to understand the relationship between sections.

IMPACT
High-frequency actions required unnecessary navigation decisions during live selling.

DESIGN DIRECTION
Prioritize Register and Inventory, clarify the relationship between operational and administrative tabs, and automatically surface the active event.

WHAT WORKED

Category navigation supported fast product selection
The use of product categories for quick access.

EVIDENCE

The user frequently relied on category filters to locate products quickly during live transactions.

VALUE
The interaction reduced searching and supported quicker checkout.

DESIGN DIRECTION
Preserve the category-first browsing structure and keep categories easily accessible in the Register. Instead of common emojis, considering designing visually recognizable icons.

FINDINGS TO NEXT ITERATION

phone.

(917) 306 5513

email.

hiulamhilaryc@gmail.com

find me @