Shape01Docs
Shape01 Docs

How Shape01 works across web, app and gym tools

This guide explains what starts on the website, what continues in the app, and how users, chats and gym tools stay connected.

What Shape01 Is

Shape01 is one product that connects chat, personal direction, routine and ongoing follow-through. The website handles first contact and clarity, while the app holds the full working experience.

  • The website introduces the product, hosts legal pages and can open the first chat.
  • The app is the full workspace for chat, profile, tracking and deeper product flows.
  • Users do not restart from zero when they move between web and app.
Getting Started

Users can begin with a quick chat on the website, then sign up with email or Google and continue with the same identity into the app. The flow is built to reduce friction at the first step.

  • A guest can open an initial conversation before creating a full account.
  • Upgrading the account preserves the conversation and user context.
  • The handoff into the app keeps the same user and the same active thread.
How Chat Continuity Works

Chats are stored under each user in Firestore, so context stays intact. Both the website and the app work against the same thread model rather than separate conversation systems.

  • Every thread is stored under the user inside `chatThreads`.
  • The website sidebar reads the same existing threads without duplicating logic.
  • Continuing into the app keeps the same active conversation.
Website vs App

The website is meant to be fast, clear and SEO-friendly. The app is meant for continuous product use. This separation keeps both surfaces cleaner and stronger.

  • Website: landing, docs, privacy, terms, signup and fast product entry.
  • App: the full Shape01 working experience.
  • Legal pages stay in Next.js and are not delegated to Flutter.
Gym Owners

Shape01 includes a dedicated gym-owner surface with a dashboard, profile, map and public page. The goal is to support both internal management and external web visibility.

  • A dashboard for members, invites, access code and package status.
  • A gym profile for the public page, displayed price, image and map publishing.
  • A public map and gym pages for discovery and promotion.
Accounts, Billing and Privacy

Identity stays in Firebase, billing remains inside the correct product layer, and privacy / terms stay permanently available on the website. This keeps a clean boundary between marketing, legal and product.

  • Google and email sign-in run on the same Firebase project.
  • Privacy Policy and Terms remain public HTML pages on the site.
  • Gym owners can view billing preview and manage web visibility from the website.
FAQ

Why are the website and the app separated?

Because the website should stay fast, readable and SEO-friendly, while the app should carry the deeper product experience without marketing noise.

What carries over from the website into the app?

The same user, the same Firebase identity and the same active thread. The handoff is designed to feel like a continuation, not a restart.

How does a gym get a public web page?

The gym owner manages profile and map visibility through the web surface, and once the profile is complete and published, the gym can appear on the map and on a dedicated public page.