I’m building a native mobile application that makes buying sports-event tickets effortless, and I need a complete UI/UX package that feels modern and minimalist on both iOS and Android. The user journey is already mapped out; what I require is a polished visual and interactive layer—from wireframes through hi-fi screens and clickable prototypes—ready for hand-off to my developers. in addition, access to News section, and Webstore that sell Merchandising is absolutely necessary. the news will read news article from a database and publish them dynamically. The website, will inquire through API about categories, and display items/prices per category, and help add to cart. Ticketing Cart & Merchandising carts cannot be miexed. Core flow to design Users will sign up or sign in (OTP, “forgot password,” first/last name fields), browse tournaments, drill down to individual matches, and study a dedicated Match screen. They must accept Terms & Conditions, view a dynamic seating chart, select seats, add them to the cart with price and seat details shown, then confirm the order. Each ticket collects holder data (first/last names and phone number) before a final review where a payment method is chosen. The app hands off securely to a web payment gateway, then returns to either a decline screen or an approved screen that issues and displays the ticket. After purchase, a profile menu lets fans change their password or pull up current bookings, displaying tickets on demand or resending them by SMS. Helpful notes • Native feel is key, so please follow Apple HIG and Material guidelines while keeping a consistent minimalist brand line between platforms. • I value clear micro-interactions—loading states for seat maps, error handling on payments, subtle animations where they add clarity. • Accessibility (font scaling, color contrast) must be baked in from the start. Deliverables 1. User flow diagram and low-fidelity wireframes for approval 2. Complete high-fidelity UI screens (Figma, Sketch, or Adobe XD) for iOS and Android breakpoints 3. Interactive prototype demonstrating every path—including decline and success states 4. Component library and style guide (colors, typography, icons) 5. Export-ready assets and hand-off notes for developers If this sounds aligned with your skill set, let’s discuss timelines and milestones so I can get this into development quickly.