Case study
Lint
Led frontend on sign-in, admin, and core shopping surfaces — delivered in a 5-day team sprint at Masai.
Lint is a team-built full-stack e-commerce application inspired by large retail experiences, focused on product discovery, detail pages, authentication journeys, and cart workflows for apparel and lifestyle categories.
- Role
- Role · Frontend lead — authentication, admin panel, product listing, and product detail (team of 5)
- Timeline
- Timeline · 2022 · 5-day collaboration sprint
- Status
- Live
- Delivery
- Team sprint
- Timeline
- 5 days
01 — Problem
What problem does it solve?
Shoppers need a responsive catalog-to-cart journey, while engineering teams need modular frontend architecture and API-backed state that can be delivered quickly under strict deadlines.
02 — Origin
How the idea took shape
Lint was delivered during an intensive team sprint at Masai School. The goal was to collaboratively build a production-style commerce workflow in five days, splitting ownership across frontend, backend, and admin surfaces while maintaining delivery quality.
03 — Role
My role
- Led frontend on sign-in, sign-up, and admin panel flows alongside core shopping surfaces.
- Owned implementation of the all-products listing page with filtering and browsing flows.
- Built product detail experiences and coordinated integration boundaries across auth, cart, and backend APIs.
04 — Challenge
The challenge
- Designing fast catalog browsing for many product cards while staying responsive across breakpoints.
- Coordinating page-level frontend ownership with backend and admin-panel deliverables in parallel.
- Maintaining clean UI-state transitions across listing, details, and cart journeys within a short sprint.
05 — Approach
The approach
- Used React component composition to separate listing, filtering, and details concerns.
- Integrated API-driven product data and routed interactions through predictable page states.
- Applied Chakra UI patterns for rapid yet consistent UI delivery under timeline pressure.
- Focused on responsive layouts to preserve browsing usability on mobile and desktop.
06 — Outcomes
Key outcomes
- Shipped a deployed full-stack e-commerce product with end-to-end user flows.
- Delivered key customer-facing pages and admin surfaces within the sprint window.
- Strengthened team leadership and deadline-driven delivery before Omniful.
07 — Differentiator
What makes this different
- Shows team leadership and sprint delivery before production SaaS work — not just solo tutorial projects.
- Frontend ownership on commerce-critical surfaces: auth, admin, listing, and product detail.
- Combines responsive UX implementation with API-backed product experiences under real deadline pressure.
08 — Gallery
Product screens
