Owned-product case study
Spellexo: building a product around the real constraints of 3D commerce.
Spellexo is one proof point within Double Edged's broader rendering, animation, asset-production and custom-experience practice. It shows what changes when a studio must own the product strategy, interface, 3D pipeline, engineering, launch and operation—not just hand off a visual.
- Product
- Interactive 3D and browser AR for commerce
- Double Edged scope
- Strategy, UX, 3D pipeline, engineering and operation
- Delivery model
- Hosted product plus managed asset preparation
- Evidence status
- Live-product capability; no commerce-lift claim
The brief
Make premium product detail explorable without replacing the buying flow.
The product question was not simply how to display a GLB. Premium materials, scale and construction had to remain credible while the experience stayed optional, worked across real commerce journeys and did not ask every visitor to load a viewer before showing intent.
The resulting product combines a click-to-load storefront entry point, interactive viewing, real-scale AR, variant mapping and a managed route from source imagery or 3D assets to a published product experience.
01
Concept and product strategy
Start with a purchase question, not a viewer feature list.
The founding problem was the gap between polished product imagery and the information a shopper can inspect for themselves: form, finish, construction and scale. Double Edged shaped Spellexo as a focused commerce product rather than a generic 3D showcase.
The strategy pairs hosted software with managed asset preparation. A merchant can begin with an existing presentation-ready model, finished renders or product photography, while the production path handles preparation when the source is not ready for a browser.
02
Experience and interface design
Keep the familiar product page; add an intentional inspection path.
The standard experience adds a lightweight “View in your home” action while existing photography, product options and checkout remain where shoppers expect them. The shopper decides when to open the interactive layer, rotates and inspects the product, and can move into real-scale AR on a supported path.
That choice makes progressive disclosure part of the UX: the default page remains familiar, and the richer interaction appears when the product question warrants it.
03
3D asset pipeline
Treat asset readiness as a production system, not an upload field.
The pipeline accepts different starting conditions: final product renders, product photography or presentation-ready 3D. Assets are reviewed and prepared for interactive delivery, including material fidelity, scale, orientation, variants and browser constraints.
Spellexo's proprietary format carries the finished visual treatment into the live experience. The important product lesson is broader than the format: source quality sets the ceiling, and artist review remains part of a credible web-3D workflow.
04
Engineering and implementation
Move viewer work behind demonstrated shopper intent.
The storefront integration places the entry control on the product or variant page but does not initialize the viewer during the initial page load. After the click, the viewer opens in an iframe and the delivery layer takes responsibility for the interactive session.
This architecture means the viewer adds no viewer-related work to the initial storefront load. It does not eliminate the need to test the opened experience: model weight, device capability, browser behavior and AR support still require explicit acceptance criteria.
05
Testing and launch
Launch the smallest complete product experience, then instrument it.
The public product supports a one-product starting point so a merchant can evaluate the experience on a real SKU before expanding. Launch readiness spans visual review, scale, interaction, mobile behavior, browser coverage, AR paths and the host product page before and after the integration.
The testing model separates initial-page performance from opened-viewer performance. It also separates technical activation from commercial impact: engagement, add-to-cart, conversion and returns should be measured against a suitable control rather than assumed from category data.
06
Ongoing operation
A product is the workflow that continues after launch.
Operating Spellexo means maintaining the viewer and delivery layer, onboarding and reviewing product assets, supporting variant mappings, monitoring device and browser behavior, and keeping commerce integrations and customer guidance current.
That operating perspective informs Double Edged's bespoke work: handoff, observability, content ownership, fallback behavior and the cost of future catalog changes belong in the scope from the beginning.
07
Lessons
What owning the full product changed.
- Load by intent. Rich 3D does not need to become initial-page work.
- Qualify the source. A viewer cannot repair inaccurate geometry, scale or materials.
- Design the operating path. Variant mapping, publishing and future asset updates are product features.
- Separate capability from outcome. A live experience proves execution; commerce lift requires controlled evidence.
- Scope the right solution. A hosted viewer and a bespoke rules-based configurator solve different problems.
08
Evidence boundaries
What this case study proves—and what it does not.
It proves that Double Edged can conceive, design, build, launch and operate an owned 3D-commerce product, including its asset and implementation workflows. It supports relevant conversations about interactive viewing, AR, product UX and technical delivery.
There is no measured Spellexo conversion or return-rate result published here, and no named merchant testimonial is implied. The product also does not prove rescue or migration outcomes for an existing configurator; those claims require separate project evidence.
Device reach and opened-viewer responsiveness remain claims to verify against a current tested browser/device matrix. Double Edged will not convert those capabilities into universal guarantees.
What it demonstrates
Product ownership, selectively applied.
- Product and commercial strategy grounded in a real buyer journey
- Interface decisions tied to performance and progressive disclosure
- A managed bridge between visual production and web-ready assets
- Engineering, launch criteria and ongoing operating responsibility
Evidence basis
Sources and claim controls
- Spellexo public product page, reviewed 26 August 2026.
- Founder product brief and click-to-load/iframe clarification, reviewed 6 August 2026.
- Double Edged interactive-products page, current site source.
Your product is a different system
Use the proof; do not copy the scope.
Map your rules, assets, integrations and operating requirements first. The estimator will show the drivers that determine whether you need a hosted viewer, an asset engagement, targeted repair, paid discovery or a bespoke build.