Raffle app

My Role As the sole product designer, I was responsible for everything from initial ideation to final prototyping. I led the research, defined the product logic, mapped out user journeys, and built the complete interface from scratch. This included low- and high-fidelity wireframes, visual identity, UI components, and responsive layouts. I also created the design system that would later scale into the native mobile versions. Design Process I started by identifying the core pain points experienced by both raffle organizers and participants. These included the manual tracking of sold numbers, low trust in transparency, and the clunky way people had to handle payment confirmations. I conducted informal interviews and observations to understand the flow and dynamics of raffles typically run in Latin America. With this understanding, I began sketching ideas that balanced simplicity with functionality. Wireframes were essential to validate flows like: creating a raffle, managing active raffles, selecting numbers as a buyer, and tracking raffle outcomes. I made sure each feature could work efficiently on mobile since most users would access the app on their phones. The visual design focused on building trust. I designed an interface that was clean, direct, and action-oriented, using clear buttons, visual cues, and short, supportive microcopy. Typography, color hierarchy, and spacing were all optimized for clarity and readability. Interactive prototypes were created to simulate the full user journey, from signing up to selecting a number in a live raffle. This helped validate the logic and usability of key interactions, including edge cases like what happens when two users try to reserve the same number simultaneously. Key UX Challenge: Number Picker Logic One of the most complex design problems was the number selection screen. Raffles could contain anywhere from 50 to over 1,000 numbers, and I needed a way for users to browse, select, and confirm numbers quickly without confusion. After reviewing common UI patterns like dropdowns, carousels, and search bars, none proved effective at scale. I ended up designing a new component: a responsive grid system with fixed headers, real-time availability indicators, and dynamic status feedback (e.g., reserved, sold, or available). This gave users the confidence and speed they needed when choosing numbers—especially in time-sensitive raffles. The design is still being iterated based on ongoing user testing, but early feedback has been positive, particularly around how fast and intuitive the selection feels.