MobileX

A modular product system for a headless, white-label mobile commerce platform

E-commerce

2023–2024

Summery

Mobilex is a B2C e-commerce platform for mobile and technology products, built on a headless, white-label architecture. As the sole product designer, I owned the experience end-to-end — from the core shopping flow and product pages to the desktop experience and new discovery features like Xplore. The central design problem: give every product its own distinct presentation, without turning that flexibility into a maintenance burden for content and engineering.

CLIENT

Ragge Company

ROLE

Product Designer

SCOPE / PLATFORM

Web + Mobile

Challenge

Mobilex needed each product to feel distinct — its own visual identity, its own way of telling a story — while the underlying platform stayed headless and white-label, meaning the experience had to scale without a bespoke build for every product.

A single fixed product page couldn't hold that range. Designing every page independently would have solved it once and broken it at scale.

There was a second problem underneath the first: mobile and tech products carry a lot of information — specs, benchmarks, camera performance, features, brand story — and I needed that information to be explorable, not just listed.

Approach

I treated this as a systems problem, not a page-design problem.

Before the main build, I ran user interviews and usability tests to identify where the existing shopping experience created friction. I don't have retained documentation from those sessions to cite specific findings, but they were the direct reason I moved away from a single fixed template toward a modular structure — a fixed page couldn't account for the friction points I was seeing across different product types.

I designed around three constraints I set for myself:

  • Distinctiveness — each product needed room to look and feel different

  • Scalability — one structure, not one architecture per product

  • Editorial control — content teams needed to compose pages without engineering involvement

I worked with product and engineering throughout to make sure the system I was designing was actually buildable and maintainable — not just flexible on paper.

Solution

A configurable product page, built from folds. Instead of one fixed template, I broke the product page into independent, reorderable folds: hero media and purchase action, brand storytelling, color selection, real-world gallery, features, camera comparison, specs, benchmarks, and related products. Any product could enable, disable, or reorder these — so a flagship phone could lead with camera comparison and benchmarks, while another product leaned into lifestyle imagery and story.

Information matched to how it's actually used. Rather than treating specs, benchmarks, and features as one undifferentiated block, I gave each its own presentation: specs stayed scannable, benchmarks were built for comparison, camera capability got a dedicated visual breakdown. I also added an audio layer to the hero section so users could listen to product explanations while continuing to browse.

Two ways to browse. I designed a conventional listing for users who want to scan and compare directly, and a second, visual-first listing built around image-led discovery for users browsing more casually. Same catalog, two entry points.

A homepage with the same logic. I applied the same fold-based thinking to the homepage — independent, rearrangeable sections instead of a fixed banner-plus-grid layout — so the entry point to the store had the same flexibility as the product pages themselves.

Desktop, without a second content system. When desktop was added after the mobile-first launch, I adapted the existing layouts and content — including imagery that had already been shot and sized for mobile — into responsive desktop layouts, instead of requiring a parallel asset pipeline.

Xplore — a second discovery layer. Alongside the core shopping system, I designed Xplore: a video-driven space for product-related content beyond official specs and written reviews. I led two iterations (MVP and a later redesign), covering the content feed, video previews, product tagging, and the post creation flow. Where the rest of Mobilex was built around users who already know roughly what they want, Xplore was built for users still deciding — a discovery layer that fed into the same product pages.

Outcome

The fold-based system meant new products could get a distinct presentation without a new page architecture — the same structure supported very different content mixes, from spec-heavy flagship launches to story-led lifestyle products, without engineering rebuilding the PDP each time. Content teams could compose and reorder folds independently, without needing engineering involvement for each new product page.

That same architecture carried through the rest of the product: the homepage, the desktop expansion, and Xplore were all extensions of one underlying content model rather than separate systems bolted on.

I continued iterating on Mobilex across Homepage, PLP, PDP, Search, Comparison, Purchase Flow, and Account for the duration of the project. I don't have reliable source data for business metrics on this project, so I'm not including any here.

The system delivered on its core promise: content teams could genuinely compose product pages independently, without engineering in the loop for every new product. But that same flexibility created a real risk — teams sometimes combined folds in ways that hurt the page's coherence or usability, since nothing in the system enforced which combinations actually made sense together. I addressed this by defining constraints on which fold combinations were valid, which resolved the issue, but it was a gap I hadn't anticipated when I first designed the system as fully open-ended. If I were building this again, I'd design those constraints in from the start rather than adding them reactively.

Create a free website with Framer, the website builder loved by startups, designers and agencies.