DFYNE · Feature case study

Search

DFYNE's search asked you to guess. You typed, saw nothing, and had to commit to a full page load to find out whether the thing you wanted existed. I rebuilt it to answer while you type.

0
Products the old search showed before you committed
0
Ways a query is understood — garment, collection, colour
0
Results shown before you finish the word
Role
Product / UX designer — concept into production
Team
Shopify developers, merchandising
Platform
Shopify (Liquid) — desktop & mobile web
01 — What it was doing before

A redirect wearing a search box.

The panel dropped from the top of the page with a search field and a row of popular-search pills. The pills mixed garment types with collection names, which is how customers arrive. But they were links. Tapping one left the page.

The field itself did nothing until you submitted. Type "leggin" and the panel showed a single line — Show all results for "leggin" — and then several hundred pixels of white. No image, no product name, no result count. The interface had the answer and declined to show it.

That is a search that cannot fail informatively. If the query matched nothing, you learned that after a page load. If it matched forty things, you also learned that after a page load. The cost of asking was the same either way — so the rational move was not to ask.

Before — mobile. Six letters typed, nothing to say.
02 — Answer while they type

The panel stays put and fills the other half.

On desktop the panel takes the right half of the window and splits in two: suggestions on the left, live product results on the right. The page behind stays where it was, so a search is no longer a departure — you can look, decide it was not what you meant, and carry on.

Results update on each keystroke and carry the things that decide a click: image, name, colourway, price. A Show all results link stays at the foot of the suggestions, so nothing was taken away — the page load simply stopped being the only route to an answer.

DFYNE search panel open on desktop with the query shorts — suggestions on the left, six results on the right
The typed word stays plain and the collection name is the completion — so the eye lands on what it did not already know.
03 — Three axes

Suggestions that know a range from a garment.

Type shorts and the suggestions are not variations on the word. They are impact shorts, dynamic shorts, defy shorts, vision shorts — the garment crossed with every collection that makes one.

This is the mega menu's argument in a different control. A large share of customers arrive holding a range name they heard from an influencer. A search that treats Impact as an ordinary string throws that away; one that completes it turns a half-remembered name into a route. It also works in the other direction — someone who only knows they want shorts is shown, for free, that shorts come in four ranges. The catalogue teaching itself without a landing page.

Colour arrives in the results, not the filters

"pink leggings" is a colour and a garment in one query, and the search resolves both rather than matching neither.

Every result card names its colourway under the product title — Hibiscus, Light Rose Pink, Espresso, Copper, Graphite, Winter Berry. At a brand where a returning colourway is a marketing event, that word is not a spec, it is the reason for the purchase, and it belongs where the decision is made.

DFYNE search on mobile with the query pink leggings — suggestions and a two-up grid of results naming each colourway
One query, two axes

pink leggings offers leggings pink, baby pink leggings and impact leggings light rose pink — the same three axes recombined: garment, colour, and the collection that happens to make it in that colour.

The alternative was the journey the old site had, and the one the mega menu also removed: land on a listing page, open the filter panel, find colour, apply it. Search collapses that into the sentence the customer would have said out loud.

04 — Density, and the empty state

Looking and hunting are different jobs.

The results grid has a two-up and a three-up state, switched beside the result count. It is an unusual thing to ship in a search panel and it earns its place: a customer who knows the product wants to scan as many as fit; one who is deciding wants the garment big enough to judge. The suggestion column holds its width and position, so the toggle changes the answer's resolution without rearranging the question.

The same shorts search in three-up density, nine smaller cards, suggestion column unchanged
Three-up. Only the resolution of the answer has changed.

The empty state has a job

An open search box with nothing typed is the most common state the panel is ever in, and the old one filled it with five pills. The new one splits it: Popular searches keeps the pills, and Popular right now fills the other half with four editorial tiles. Two are womens and two are mens, so the panel does not assume which side of the catalogue the customer is on before they have typed a character.

DFYNE search panel with an empty query — six popular search pills and four editorial tiles
Nothing typed yet, and the panel is already useful.

The same panel on a phone

Mobile takes the full screen rather than a half-panel, and keeps the order — suggestions, the link out, then results. The density toggle survives, which matters more here than on desktop: two-up on a phone is a genuinely different browsing speed from three-up.

The field keeps a Clear action inside it rather than making the customer hold backspace — the difference between refining a query and abandoning one.

After — mobile
05 — The calls

The answer goes in the panel, not behind a page load

Instead of

Leave the panel as a doorway and improve the results page it led to.

Why

The old panel charged the same price — a full navigation — whether the query matched forty products or none. Answering in place removes the cost of asking, which is the thing suppressing the behaviour.

Cost

The panel now loads product imagery on every keystroke, so it is considerably heavier than a list of links and has to be throttled to stay quick.

Suggestions complete into collection names

Instead of

Treat the query as plain text and match it against product titles.

Why

Marketing is collection-led. Completing "shorts" into impact, dynamic, defy and vision turns a half-remembered name into a route — and teaches the customer who only knew the garment that four ranges make one.

Cost

The suggestion vocabulary has to be kept current. A range that has not been added is invisible to the customer arriving with its name.

Two result densities rather than one

Instead of

Pick a single grid and commit to it.

Why

Scanning and deciding are different jobs. One customer wants as many as will fit; the other wants the garment big enough to judge the fit and the colour.

Cost

A control the customer has to notice, and a preference the interface has to remember. It has to earn its place every time.

On results

Directional, and I would rather say so: I no longer have access to the analytics to put a number on this one. The change that is measurable in principle is the cheapest to state — the old panel could not show a result without a page load, and the new one shows six before you have finished the word.

Next
Quick add →

Average order value up 13%, items per order up 20% — by building for the set rather than the garment.

declanamalone@gmail.com