Conversion-Led UX & Wireframes
Wireframes for home, collection, product, cart and checkout drawn from your own session recordings, site-search logs and support tickets. Not a template library.
A Dubai storefront has to mirror properly in Arabic, sell without a postal code, and stop treating cash on delivery as the default.
Delivered remotely for brands across Dubai and United Arab Emirates.
Almost every Dubai store we open has the same two structural faults, and neither is cosmetic. The Arabic side is a translation layer draped over a theme that was never built to flip direction, so the moment a shopper switches language the grid stops reading right, the cart drawer opens from the wrong edge, and the filter labels stay in English. And the checkout treats cash on delivery as the normal path, which quietly decides the rest of your business: refused deliveries, cash handled twice, no card on file, and a customer you cannot build a retention programme around.
We build both directions as one storefront rather than a primary and a translation. That means navigation, facets, badges, carousels, form fields, invoices and transactional email all mirror, and it means the Arabic path gets QA'd on real devices instead of assumed to work because a translate app reports full coverage. Third-party apps are where this breaks — a review widget or a size-chart app injecting its own left-to-right markup will undo a week of theme work, so app selection becomes a design decision here, not an afterthought.
Then the catalogue. The categories Dubai actually produces each break a stock theme in their own way. An abaya or modest-fashion line needs made-to-measure inputs, fabric and drape detail and length options structured as real variants and metafields. Fragrance and oud need discovery sets and decants merchandised as the entry point, because nobody buys a AED 600 attar blind. Fine jewellery needs pricing that can follow the metal rate and fraud rules that do not decline your best orders. We design the templates around the category rather than asking the category to survive a template.
Two things about a UAE build catch teams who have only shipped for US or European stores. The first is address entry: the UAE has no functioning postal code system, so a required ZIP field, a postcode-driven rate table or an address validator built for five-digit codes will cost you orders every day. Dubai addresses arrive as building name, area, landmark and sometimes a Makani number, and the checkout and the courier handoff both have to accept that shape. The second is the calendar. The retail year here runs October through April, the summer sees a real population dip as residents travel, and Ramadan reorders buying hours so completely that traffic peaks after Iftar and again well past midnight. We scope builds to land before the season opens, not into it, and we make sure the promotional and shipping-cutoff controls your team will need through Ramadan and Eid are theme-editor switches rather than developer tickets.
The same standard of work we run for every client — applied to a Dubai brand’s realities.
Full service detailWireframes for home, collection, product, cart and checkout drawn from your own session recordings, site-search logs and support tickets. Not a template library.
A bespoke theme in clean, commented Liquid with modular sections your team can rearrange themselves. Zero dependency on page-builder apps.
Collection architecture, filtering, badging and cross-sell rules mapped to how your catalogue actually sells. Bestsellers surface; dead stock stops eating grid space.
Image pipeline, third-party script audit and app cleanup enforced against a hard budget: LCP under 2.5s on 4G mobile, CLS under 0.1, INP under 200ms.
Products, variants, metafields, collection copy and redirects loaded and QA'd in a dev store before cutover. You review a real store, not a Figma file.
Loom walkthroughs, a written theme guide and 30 days of post-launch fixes included. Your team owns the store from day one.
We do not work off a rate card. Every Dubai engagement starts with a fixed statement of work — named deliverables, named dates, one number — written after we have looked at your store, not before. If a smaller first step would serve you better, we will say so.
Get this scopedTwo weeks inside your analytics, heatmaps, site search and support inbox. We leave with a ranked list of what is currently costing you revenue.
Sitemap, template inventory and grey-box wireframes for every page type. Signed off before a single pixel gets designed.
Figma component library, type scale and every awkward state: empty cart, sold out, pre-order, bundle, back-in-stock, subscription upsell.
Liquid development in a dev store, tested on real devices and against your live app stack. Accessibility checked to WCAG 2.1 AA.
Redirect map, tracking validation, DNS cutover on a low-traffic window. Then 30 days of monitoring against the pre-launch baseline.
Anonymised under NDA. Figures pulled from the client’s own analytics.
~$6M/yr DTC, 900+ SKUs across size and colour variants, US · Shopify Plus
Returns ran at 31% and refund cost consumed the entire paid media margin. One size chart image served 40 different fits, and 62% of add-to-carts started on a collection page that never showed variant availability. The named constraint: no new product photography budget, so every fix had to come out of the existing asset library and the review corpus.
~$11M/yr, 2,300 SKUs, configurable upholstery, US · Shopify Plus + Hydrogen storefront (Oxygen)
Fabric, leg and size options turned 2,300 SKUs into more than 40,000 variant permutations, and the Liquid theme rendered a configurable PDP in 6.9 seconds on mobile. Collection filtering ran client-side, so 40% of shoppers left before the first product painted. The named constraint: the ERP stayed. It was the single source of truth for stock and lead times and was not up for replacement.
“Full rebuild in 11 weeks, launched two days before Black Friday, which was an aggressive ask and probably a stupid one on my part. They pushed back hard on three homepage ideas I was attached to and were right about all three. AOV went from $58 to $79, mostly off the bundle builder they put on the product page.”
Thirty minutes with the strategist who would actually run your account. We screen-share your store, read your data live, and tell you the three highest-value things we can see from the outside.
Prefer to write it out? [email protected] gets a real reply the same business day, Mon-Fri, 9am-6pm MT.