Context
The platform supports two connected journeys: participants browse lots and place bids while the operations team monitors and runs the event. Every update needs to reach both sides at the right moment.
The problem
Keep participants and operators synchronized during live events while making the current lot, leading value, and status of every bid easy to understand.
My role
I worked across the web and mobile frontend, translating auction rules into catalog, lot detail, bidding, and operations flows. I collaborated with backend and product to define interface states and responses.
Technical decisions
- Model bidding as explicit states so success, rejection, and concurrent updates remain visible to participants.
- Use WebSocket events to reflect new values and event changes without requiring a manual refresh.
- Share language and interaction patterns across web, mobile, and operations without forcing each surface into the same interface.
What I implemented
- Lot catalog and detail pages.
- Bidding flow with real-time updates.
- Mobile experience built with React Native.
- Dashboard for the operations team.
Outcome
The product presents catalog browsing, bidding, and operations as one coherent journey. Live updates remove the need for manual refreshes and keep the event state visible to participants and operators.
What I learned
Real-time systems need more than an active connection: the interface must make each state transition understandable and keep participants and operators aligned around the same business rules.
