Skip to content
Thnkers

Fabrico · Sewing patterns, e-commerce · International · 2026

The shop was beautiful. On a phone, it wasn't.

Timeline
3 weeks
Market
International

3

platforms — iOS, Android, web — from one codebase

What was missing

Fabrico sells downloadable sewing patterns. The catalogue is good. The brand is good. The website works. What didn't work was buying a pattern on a phone.

That's where we started.

The insight

Sewing pattern customers browse on phones. They discover a design, look at the photos, check the size range, and decide whether to buy. The decision happens quickly, on a small screen, usually between other things. If that experience is slow, confusing, or simply not pleasant to use, the sale doesn't happen. The pattern doesn't get purchased. The customer goes somewhere else, or nowhere at all.

The existing app was functional. It felt like a website that had been pressed into a smaller space. That's a different thing from an app that was made for a phone from the start.

What we built

We rebuilt the app from the beginning on React Native and Expo, with a design system created specifically for how Fabrico's customers actually use a phone.

The home screen doesn't open on a product grid. It opens on a story: a large image, a curated selection of bestsellers, featured collections. A customer arriving for the first time sees a brand, not a catalogue dump. A customer returning sees what's new.

Fabrico patterns are sold by size and height. A size 40 in one height is a different cut from a size 40 in another. On the original app, selecting the right combination required navigating a table of options that took several steps to understand. We rebuilt the product page around a live picker: you choose your size, you choose your height, the price updates immediately. One screen, one decision, no table.

We built a ten-question quiz. It asks the customer what kind of sewing they do, what level they're at, what garments they like to make. The answers map to one of six customer types, and the result is a personalised set of pattern recommendations plus a 20% discount saved directly to the account. A customer who takes the quiz doesn't just browse; they get a starting point that feels chosen for them.

The Learning Hub, which contains the Fabrico blog, is built natively into the app. Editorial content and the shop are in the same place. A customer reading about fabric choice can buy a pattern for the fabric they've just read about without switching applications.

The profile section carries order history, a downloads library, size charts, and how-to guides. Everything a returning customer needs is in one place, behind one login.

Checkout was the hardest part to build. Stripe payment runs through a hosted page that can't be embedded inside a native app. We built a session that drives the payment in the browser, watches the order until it settles, and returns the customer to the app with the purchase confirmed and the download ready. From the customer's point of view, they paid and the file appeared. The implementation that produces that experience is considerably more complicated than it looks.

The app runs on iOS, Android, and web from a single codebase. Three weeks from start to delivery.

The Fabrico app home screen, with the story banner and a bestsellers rail of sewing patterns.
The catalogue screen: search, category filter chips and a grid of patterns with prices.
A product page for girls' shorts, with the technical drawing, price range and size picker.
The projects screen, tracking an eight-step sewing checklist with a progress bar.

Results

3 platforms from one codebase. 18 screens and routes. Approximately 4,800 lines of TypeScript. 3 weeks for the full rebuild, redesign, and delivery.

Why this holds

A pattern customer who downloads the app, takes the quiz, gets a recommendation, and completes a purchase has had an experience that is personal from the first screen to the last. That's not a loyalty programme. It's not a discount. It's a shop that felt like it was made for them, which is what sewing is actually about.

The quiz is the part of this that's hardest to copy. The recommendations aren't algorithmic in the usual sense. They come from understanding the customer's level and preferences well enough to say: start here. That requires knowing the catalogue and knowing the customer. We built both into the same screen.

What the work included

Mobile application development, design system, WooCommerce integration, iOS, Android and web delivery

Stack
React Native, Expo SDK 54, React 19, TypeScript, Expo Router, TanStack Query v5, Zustand, Reanimated, Moti, WooCommerce REST, CoCart, JWT auth, Stripe

Tell us what's missing.

Thirty minutes. You describe the pain and the result you want. We ask questions. If we can help, you get one email with what we found, what we'd build and what it costs. If we can't, we'll say so.

or write to will@thnkers.com

Not ready to talk? See what the current way costs you