Discover visually
Shop through a shoppable feed, campaigns, categories and trend-led edits.
A product retrospective by Mehul Dadlani
Fashion, at the speed of now.
My account of helping build Klydo across its consumer app, admin console, backend systems and production releases.
Enter the archive

This is how I remember Klydo: it brought trend-led fashion into a fast, visual shopping experience. People could discover a look, find the right product, and get it delivered in minutes instead of days.
I never saw it as only a storefront. It combined editorial discovery, structured categories, search, recommendations, rapid fulfillment, and a Try & Buy model designed to make online fashion feel more immediate and less uncertain.
Shop through a shoppable feed, campaigns, categories and trend-led edits.
Connect live catalog availability to a location-aware, delivery-in-minutes promise.
Let customers try selected items at home and pay for what they keep.
These campaign frames captured how Klydo introduced itself: fashion in minutes, discovery shaped by culture, and the confidence to try before committing.
01
Discovery
I worked across the feed, categories, merchandising and search so people could enter the catalog through intent or inspiration.
02
Content becomes commerce
I worked on feed campaigns, scheduled placements and stock-aware product selection that connected editorial content to products people could buy.
03
Try & Buy
I contributed to the collaborative Cart V2 foundation and improved Pay Now and Try & Buy behavior across eligibility, grouping, address and checkout states.
04
Instant fulfillment
I fixed serviceability, warehouse inventory and Try & Buy eligibility in the commerce paths behind Klydo's delivery-in-minutes promise.
05
The next visit
I shipped Recently Viewed and worked on profile, membership and referral experiences that brought useful context into the next visit.
Some of the most involved systems I worked on are preserved here as text, grounded in the product and code history rather than reconstructed UI.
Built the product-detail bottom sheet's coordinated gestures and custom physics, then added image zoom, View Similar and a curated similar-discount rail.
Rebuilt the Flutter shopping chat and integrated similarity-based product recommendations into the conversation.
Built the V2 order detail page across Kotlin view providers and Flutter Stac renderers. Backend state composed tracking, payment, cancellation, returns, exchanges, refunds and Try Now Pay Later (TNPL) actions.
Built the product-pairing graph and per-item cart carousel, then moved its copy, animation and display configuration into Cart V2.
Built admin-console surfaces for category trees, feed campaigns, search promotions, PDP curation and scheduled UI configuration, backed by role-protected APIs.
I worked at Klydo as a Product Engineer across the Flutter consumer app and admin console, Kotlin backend, selected FastAPI media work, and production support.
Customer-facing work was often paired with backend contracts, admin controls, analytics, rollout gates or the production fixes needed to keep it running.
Category pages, warehouse-aware catalog facets, Recently Viewed, feed campaigns, scheduling and admin controls.
PDP gesture architecture and zoom, View Similar, chat recommendations, and algorithmic plus manually curated product rails.
TNPL and cart correctness, Pair It With, and the V2 server-driven order detail page across tracking, cancellation, returns, exchanges and refunds.
Role-protected admin-console workflows for categories, campaigns, search promotions, PDP curation and scheduled UI.
Guest checkout, identity transitions, event delivery, retries, observability and review standards.
Image-memory fixes, lifecycle debugging, crash reporting, release automation and sustained mobile and web releases.
I built Klydo alongside a small team working through product bets, launches, production incidents and the everyday rhythm between them.
The work was shared. So were the outings, celebrations and moments around it.
On July 5, 2026, Klydo stopped accepting new orders. Its app notice said the current consumer offering was paused while the company moved in a new direction.
The Economic Times and Mint placed the shutdown inside the wider quick-fashion market. Their analysis is not presented as Klydo's disclosed internal reasoning.
Quick commerce in fashion has multiple issues, like low sell-through rates and high inventory requirements.Why isn't quick fashion working?Mint examines the capital, inventory and logistics demands behind fashion delivery in minutes, while noting that Klydo did not disclose an exact reason for the pause.
Independent retrospective
After Klydo shut down its consumer product, I created this independent retrospective to document what Klydo was and the work I contributed.
Mehul Dadlani