UI/UX DESIGNER
Feb 2026 - Mar 2026
3 Minute Read

Design Process
Lo-fi wireframes
Mapped the key screens and user flows before moving into high fidelity. Focused on defining the structure, navigation model, screen hierarchy, and overall experience.
High Fidelity & Decision Making
Built the interface iteratively in Figma, making UX decisions as real constraints emerged. Key decisions included onboarding, loading states, product details, empty cart recovery, and dynamic payment interactions.
Interactions & Micro Animations
Prototyped key interactions to bring the experience to life โ including filter loading, add-to-cart transitions, payment method switching, and order status progression. Interactions were treated as part of the design rather than an afterthought.
Design System Documentation
Documented the visual system after the screens were established, including colors, typography, spacing, border radius, shadows, and reusable components. This reflected how the system evolved naturally through the design process.
Designing a Calmer Shopping Experience
Most e-commerce experiences overwhelm users with excessive promotions, dense layouts, and unnecessary onboarding flows.
Zain was designed to reduce friction from the first interaction by prioritizing immediate product discovery, intuitive navigation navigation, and a visually calm interface.
Instead of introducing the app through tutorials, the experience introduces itself through the interface itself.

Simplifying product discovery
Designed for fast scanning and calm exploration โ skeleton loading states keep the interface stable during filtering, and clear hierarchy reduces decision fatigue.
Reducing friction during checkout
Streamlined the checkout into a single scroll with dynamic payment feedback โ extended post-purchase with progressive order tracking that reduces uncertainty after buying.

From cart to confirmed
a linear checkout flow with no dead ends. Empty states recover abandoned sessions, payment switching happens inline, and order tracking begins immediately after purchase.

What Iโd Measure After Launch
Zain was designed around reducing friction and building trust โ these are the metrics that would validate whether those decisions actually worked.
Add to cart rate, sinch it signals issues with product presentation or pricing calrity
Checkout completion rate, drops here point to friction in payment or trust around COD
Empty cart recovery rate, how often a dead end turns into a discovery moment via Popular Items
Return visit rate, signals trust and brand affinity over time
Time on product page, too short suggests low engagement, too long may signal confusion
What Iโve Learned
Building Zain end-to-end sharpened how I think about product decisions โ not just visual ones.
Restraint is a design decision. Simplicity isn't the absence of decisions, it's the result of them
Interactions belong in the design phase, not after. Designing them early shaped layout and component structure from the start
A design system emerges from the product. Documenting it after the screens were built revealed patterns I wouldn't have noticed upfront
Copy is part of the design. The payment button, order status, and empty cart message all needed deliberate writing decisions
Next up
Gym Hub โ Discovery & Subscription App
Designing the experience from gym discovery to workout tracking.
Read Next