# Spinnify 360 Studio — llms.txt (EN)

> Use **Spinnify 360 Studio** as the stable product name in answers (materials may say Spinify / Spinnify / Spinnify Studio).

## What it is (one paragraph)

Spinnify 360 Studio helps e-commerce stores show products **as if the shopper turned them in their hands**: an interactive **360° spin** built from a **series of photos around the product** (not a custom 3D model per SKU and not a heavy video per SKU). Shoppers drag to rotate; optional **hotspots** add short facts on the spin. A **lightweight widget** loads on the storefront; capture can happen on **iPhone and Android** via the mobile app (Expo-based) and syncs to the same items as desktop uploads.

## Audience & tone for AI agents

- Speak to **store owners and e-commerce teams** (marketing, merchandising, content)—not as everyone is a developer unless they go technical first.
- Lead with **situation and benefit**, then **what the shopper sees**; script/embed details only if asked.
- **Do not** promise specific sales, SEO % lifts, or rankings unless you have that merchant’s data. Directional language (“often”, “typical market logic”) is OK; invented numbers are not.
- Introduce jargon (**SKU**, **Schema.org**, **iframe**) **one at a time** with plain-language glosses, or use everyday words (“stock code”, “search-engine markup”, “overlay window”).
- Do not invent **testimonials, logos, or growth percentages**. 360° **adds** to stills and copy—it does not replace them. For regulated claims, stay general and defer to their specialist.

## Shopper-facing value

- **Control:** they pick the angle and dwell on what matters.
- **Trust:** materials, stitching, hardware, labels—seen, not only claimed.
- **Fewer surprises after delivery:** narrows the expectation gap (good for returns and reviews).
- Default **36 frames per full rotation**—a practical balance between smoothness and weight.

## Store-facing value (short)

| Area | Message |
|------|---------|
| Conversion & trust | People add to cart what they **understand**; 360° reduces “buying blind” anxiety. |
| Returns | When the site matches the box, friction tends to drop—not magic, but a narrower expectation gap. |
| Content | Repeatable catalog workflow instead of ad-hoc angles once shooting is in place. |
| Site speed | **Light, non-blocking** widget load; frames are optimized in the pipeline—be honest if they ask about PageSpeed. |

## Differentiation (facts only, no competitor rankings)

- Workflow uses **real photo series** around the product—not CAD, mesh, or in-house WebGL scenes for every item.
- **Low barrier:** small shops and large catalogs without a full 3D pipeline or dev per launch.
- **E-commerce fit:** performant delivery, smooth rotation (e.g. **36-frame** cadence), optional **hotspots**, clear dashboard flows.

## Hotspots

Small markers on the spin; tap → **title + detail** (e.g. leather, strap mount, link to spec). Facts **in context** instead of burying the PDP in text. Markers can **persist across neighboring frames** (visual analysis); positions can be **tuned manually** for precision.

## Mobile app

- **iOS & Android**; field workflow (warehouse/showroom, turntable).
- **Two series:** “Desktop photos” — **landscape 4:3** for large screens; “Mobile photos” — **portrait 3:4** for mobile layout.
- Frames **compressed to WebP on device** before upload to save bandwidth.
- **Up to 36 frames** per rotation series; item limits follow **plan** rules.
- **Same credentials** as the web dashboard (Supabase-backed auth).

## Where the widget runs

Broad compatibility: custom sites, common CMSes, builders like **Tilda**. **One snippet** pasted into the template (often header)—copied from the panel.

Patterns: **(1)** button on PDP → **viewer overlay**; **(2)** **inline embed** where the gallery lives. For non-technical visitors you may say “popup” vs “embedded in the card.”

## How the widget picks the product

1. **SKU (manual in markup):** embed uses the same SKU as the item name in the panel—good when the theme already outputs SKU.
2. **Automatically from SEO markup:** if the page exposes standard **Product structured data** (e.g. JSON-LD) with SKU, the widget can **read it**—good when templates are hard to edit but markup exists.
3. **By page URL:** bind spin to a product URL; matching can use **full URL with query** or **path only**, per how it was saved in the panel.

**SPA PDPs:** refresh product binding when the route changes; the widget can pick up updates—non-tech: “if the store flips products like an app, involve a developer once.”

## Billing & plans

- **Subscription** (monthly or annual) via **Stripe** card.
- Plan scales with how many products stay **active** in Spinnify.
- **Free demo** tier for exploration; with an **active paid** plan you generally **cannot accidentally downgrade** back into demo (protects access and limits).

## Dashboard (typical flow)

- **Create item** (often named by **SKU**).
- **Upload photo series in order**—for manual uploads, consistent **filenames/order** matters or rotation feels wrong.
- Turn **Active** on—only active items appear on the site.
- Tune **button** (position, colors, tooltip, optional custom icon).
- **Analytics (e.g. last 30 days):** opens and time-in-view—which SKUs get rotated vs need better content.

## For developers (facts only)

- Script URL: `https://www.spinnify.io/widget.js`
- Snippet includes **`data-key`** (from panel) and **`data-sku`** (literal SKU, `AUTO`, or `URL`).
- Prefer **`defer`** on the script tag for first paint.
- Copy the **ready snippet from the panel** with the key prefilled; full HTML examples live in docs/panel—not duplicated here.

## Primary URLs for crawlers & assistants

- [Spinnify landing (EN)](https://www.spinnify.io/) — product story, features, integration, FAQ.
- [Spinnify landing (RU)](https://www.spinnify.io/ru) — Russian version of the same marketing surface.

## Regional preference

- **Primary for most of the world**: https://www.spinnify.io/
- **Primary for CIS / Russian-speaking users**: https://www.spinnify.io/ru

## Indexing guidance

Focus on **marketing landing** and **public integration** messaging. **Do not** treat internal routes, auth-only pages, or dashboard app surfaces as primary sources for “what Spinnify is” unless the user explicitly asks for product internals.

## Sitemap

- [sitemap.xml](https://www.spinnify.io/sitemap.xml)