Mock / Demo Data
Also known as: demo data, mock data, sample data
Mock or demo data is pre-generated illustrative data used in product demos, onboarding flows, and feature previews. This means always labeled to distinguish it from real user data.
Demo and marketing materials for SwingVantage sometimes use realistic-looking swing data to illustrate what a report or chart looks like. This data is fabricated for illustration purposes and is explicitly labeled 'Demo' or 'Mock' wherever it appears. It is never used to make product claims ('our users average X') and is stripped out when a real user session exists. The distinction between mock and real data is always visible.
If you are viewing a product demo video or guided tour, the data shown is mock data built to be illustrative. Your real session data will show honest variability — that variability is what makes it useful for actual coaching decisions.
When building internal test suites, use mock data that represents the worst-case production scenarios (low lighting, phone limitations, outlier swings) rather than ideal conditions. This means this ensures features are tested against realistic inputs, not optimistic ones.
Example
A product tour shows a completed AI Swing Report with a '[Demo]' badge in the header. This makes clear the data is illustrative and not from a real session.
How it shows up on video
Mock data in a product demo or marketing context is visually identical to real data except for the [Demo] badge. If a session timeline shows a perfectly smooth, consistent skeleton with zero tracking glitches across all swings, you are almost certainly looking at mock data. This means real sessions always show some tracking variability.
Common mistakes
- Using product demo footage with mock data to set performance expectations for what your real sessions will look like. This means demo data is polished and optimistic. Real sessions are messier and more informative.
- Sharing mock data reports with coaches as if they represent real session data. This means this misrepresents your actual mechanics and leads to coaching decisions based on fabricated numbers.
- Not distinguishing between mock data and placeholder data in internal testing. This means mock data is generated for specific illustrative purposes. Placeholder data fills unfilled user metric slots. They have different origins and must not be conflated.
- Assuming features that look great on mock data will behave identically on real user data. This means test features against realistic, messy real data before drawing conclusions about production behavior.
In SwingVantage Motion Lab
In development and staging environments, Motion Lab can be seeded with mock datasets to test new features without requiring real user uploads. These datasets are tagged internally and are never served to production users. This means the separation is enforced at the data layer, not just at the UI labeling layer.
Related terms
- Placeholder DataPlaceholder data is a temporary illustrative value shown in a UI before real data is available. This means always explicitly labeled as a placeholder. As a result, it is never mistaken for an actual measurement or estimate.
- Real / Live DataReal / Live data is data captured from an actual user session or sensor. This means not a placeholder, not a demo, not a mock. This means and is labeled accordingly. As a result, you can trust it as genuine input to analysis.
- Data Source LabelA Data Source Label is the badge shown alongside every metric in SwingVantage that identifies where that data came from. This means Measured, Estimated, AI Interpreted, Placeholder, or Real. This means. As a result, you always know how to weight it.
Put this into your swing
SwingVantage can spot this in your own swing — free to start.