In phygital sports, the physical and digital parts aren't separate layers. They are one competition running on two fields at once.
Not every format has two stages. Football, basketball and shooter run a digital round then a physical round, while dancing is scored by the game engine during the physical performance itself.
A platform only works if player identity, timing, scoring and event state stay consistent everywhere someone is watching or playing.
AR, VR, IoT, motion tracking, mobile apps, computer vision and real-time cloud infrastructure each solve a different problem. No product needs all of them.
The money often sits outside the tournament: training, fan engagement, sponsorship, venue technology and content.
A good MVP doesn't chase every emerging technology. It needs one competitive mechanic that works every time, and indicative build costs start in the tens of thousands of dollars, not millions.
Real-time architecture and an operational fallback matter as much as how immersive the experience looks.
Privacy, accessibility, device compatibility and fair-play controls belong in the requirements from day one.
When choosing a partner, judge systems integration, live-event reliability and operational thinking. Nice 3D visuals are the easy part.
For years, sports technology meant adding digital capabilities to physical sports. Scores moved from paper to platforms, wearables began capturing athlete performance, and mobile apps gave fans live statistics, highlights and personalised content. Augmented reality (AR) brought digital information into venues, and virtual reality (VR) opened new ways to train and to watch.
Phygital sports go a step further. Instead of adding a digital layer on top of a physical sport, they connect physical competition and digital gameplay as parts of the same contest. Players, rules, scoring, data and progression can span both environments. In the best-known formats, athletes play a video game version of the discipline and then a real-world match, and both results decide the winner.
The scale of the category is now hard to ignore:
This creates a specific technology challenge. A sports app can show a live score. An AR app can overlay statistics on a venue. A VR app can simulate a pitch. A phygital sports platform has to connect all of these so that physical activity, digital gameplay and real-time data work as one competition.
This guide explains how phygital sports work, what technology sits behind them, where the commercial opportunities are, what they cost to build, and how to avoid the mistakes that sink most first attempts.
Phygital sports are hybrid sports experiences that combine digital gameplay or digital interaction with physical athletic competition, governed by shared rules that decide how each part contributes to the result.
The two best-known structures are:
For example, Phygital Football at Games of the Future pairs a video-game football match with a real 5v5 match, and performance in both counts towards the result.
How phygital sport differs from neighbouring categories
| Format | Physical activity | Digital component | Shared competitive system |
|---|---|---|---|
| Traditional sport | Yes | Low / optional | Yes |
| Esports | No | Yes | Yes |
| AR sports experience | Yes | Yes | Sometimes |
| Connected fitness | Yes | Yes | Usually |
| Sports simulation | Optional | Yes | Yes |
| Phygital sport | Yes | Yes | Core to the format |
Phygital sport vs esports. Esports are competitions played entirely through video games. In phygital sport, the physical performance is a required part of the contest, so an athlete can't win on gaming skill alone. This is also why the technical challenge is different. An esports platform manages digital events, while a phygital platform has to reconcile digital events with what happens on a real court, pitch or dance floor.
The term is sometimes used more loosely for any experience where physical and digital touchpoints work together. For technology buyers, it's useful to distinguish between a phygital competition and a broader phygital sports experience. That distinction prevents a common product mistake: building an impressive digital layer without defining what role it plays in the sport.
A useful test is to ask four questions:
If the answer to all four is yes, you are much closer to a true phygital sports product than a conventional sports app with immersive features.
The World Phygital Community currently oversees four core ranking disciplines: Phygital Football, Phygital Basketball, Phygital Dancing and Phygital Shooter. Each one poses a different engineering problem.
| Discipline | Digital element | Physical element | Structure | What the platform must handle |
|---|---|---|---|---|
| Phygital Football | Competitive video-game football match | Real-world 5v5 match | Sequential | Carrying results between stages, combined scoring, substitutions |
| Phygital Basketball | Console basketball gameplay | Real-court 2v2 match | Sequential | Fast rotations, per-player identity across devices, live score sync |
| Phygital Shooter | Team-based tactical rounds across two maps | Real-world laser tag | Sequential | Team state, round timing, hit detection, disconnect recovery |
| Phygital Dancing | Dance game scoring on screen | Athlete performing physically, tracked by controller or motion capture | Blended | Low-latency capture, fair and consistent scoring, elimination brackets |
Both use the classic two-stage model: a digital contest followed by a physical one. The platform's hardest job is the hand-off. Identity, score and match state have to survive the move from consoles to the court, often with substitutions, timeouts and penalties in between.
Matches unfold in two stages: fast-paced digital rounds across two maps, then a real-world laser-tag game. That adds a third data source, hit detection, alongside game events and referee input.
At Games of the Future, sixteen athletes compete in a double-elimination format, and matches are best-of-three tracks. Dancers use a Just Dance title on Nintendo Switch, and the game scores how accurately they copy the on-screen moves (Games of the Future). The WPC's own description adds that competitions run on a technical field with screens or projectors, with motion capture systems tracking participants (WPC). For builders, this is the format where real-time capture and consistent scoring matter most.
Why this matters for product teams: "phygital" isn't one architecture. A sequential format needs robust state hand-off. A blended format needs low-latency measurement of physical movement. Your first design decision is which of these patterns your sport uses.
Phygital sports have moved well beyond a purely conceptual discussion.
Competition scale. Games of the Future 2026 took place in Astana from 29 July to 9 August, with more than 800 participants from over 50 nations across eight disciplines and a prize pool above US$4 million. Organisers expected more than 100,000 spectators across four venues. Four of the eight disciplines are core phygital formats. The others include Phygital Fighting, MOBA (on PC and mobile) and Battle Royale.
A real competitive pathway. Athletes qualify through regional (Phygital Origins) and national (Phygital Rivals) tournaments, with a final qualifier tier called Phygital Contenders. That means organised rankings, broadcasts and event operations, and all of that needs software.
A wide device footprint. Current implementations involve:
That means the opportunity is increasingly an integration problem, not just a game-development problem.
A sports organisation planning a phygital product should think about the whole chain:
Athlete → device → data → scoring → operator → audience → sponsor → analytics
That is the system that has to work.
The flow below describes a sequential format, where a digital stage is followed by a physical one. Not every phygital sport works this way. In a blended format such as Phygital Dancing, the game scores the athlete's physical performance as it happens, so there is no separate hand-off between stages.
For platform teams this changes the architecture:
Most of what follows applies to both. The rules layer, the single authoritative match state and the failure-mode testing are essential either way.
The system needs to know:
Identity sounds basic until a tournament contains multiple devices, substitutes, operators and concurrent matches.
A single player ID may need to connect a console account, mobile profile, wearable session and physical participation record.
The digital stage may involve:
The choice of game engine depends on the competition mechanic, target devices and level of interaction required. For experiences that require custom 3D gameplay, physics, real-time interactions or integration with connected devices, Unity game development can provide a flexible foundation for building the digital competition layer.
The digital stage generates measurable events.
Examples include:
The platform then needs to convert raw events into authoritative competition data.
For example:
This is where product engineering becomes important.
A game client should not automatically become the final source of truth simply because it generated an event.
A production system may need:
This is often where the experience becomes operationally difficult.
The system may have to carry state from the digital stage into the physical stage.
Depending on the rules, this could mean carrying a:
The physical stage then produces a new stream of events.
The scoring engine combines valid events from both stages.
A simplified version looks like:
Digital Score + Physical Score = Final Competition Score
But the production implementation is more sophisticated because the system must account for:
For a normal mobile app, delayed state can be annoying.
For a competitive phygital event, inconsistent state can become a fairness problem.
Imagine:
The visual problem is obvious.
The real problem is that the system has no single authoritative event state.
That is why the scoring and event architecture should be designed before the visual layer.
Phygital sports do not require every emerging technology. The right architecture depends on the competition mechanic.
A mobile application can serve as the participant and fan layer.
Typical functions include:
For many products, mobile is the most practical starting point because it avoids requiring every participant to wear specialised hardware.
Businesses planning the participant experience can also benefit from a dedicated mobile app design approach that maps the journey before development begins.
AR is useful when the physical environment remains important.
Examples include:
VR is more appropriate when the user needs to enter a simulated environment.
Examples include:
Building these experiences requires more than adding a 3D layer. Device compatibility, interaction design, spatial tracking, performance and integration with the wider sports platform all need to be considered. An AR VR app development company can help connect the immersive experience with the participant, venue and real-time data layers.
The important product decision is not “AR or VR?”
It is:
What part of the sports experience actually benefits from immersion?
IoT becomes valuable when physical activity needs to generate digital events.
Potential data sources include:
Connecting these devices to a reliable software platform requires more than collecting sensor data. An IoT app development company can help design the communication layer between connected equipment, device gateways, event-processing systems and the applications that use the resulting data.
A typical flow might look like:
Sensor / Device → Device Gateway → Event Ingestion → Rules & Scoring → Real-Time API → Apps / Dashboards / Broadcast
AWS IoT Core is one example of a cloud IoT platform built for secure, two-way communication between connected devices and the cloud. It also supports device-shadow patterns, which can help applications maintain a representation of a device's last known state when the device temporarily goes offline.
For phygital products, that matters because real-world equipment is not always online, stable or available at the exact moment an application requests its state.
Computer vision can reduce the need for dedicated sensors in certain scenarios.
Possible applications include:
The trade-off is important.
Computer vision can simplify physical hardware requirements, but it introduces its own challenges:
For a high-stakes competition, automated detection should also have a defined fallback path.
Participants, referees, venue operators and viewers may all need rapidly updated state.
A robust real-time system typically separates:
That separation makes the platform easier to debug and scale.
It also reduces the risk of allowing one front-end application to become the unofficial source of truth.
This is one of the most important components.
Instead of embedding competition logic throughout the application, maintain a dedicated rules layer.
Conceptually:
Raw Event
↓
Validate
↓
Apply Rule
↓
Update Match State
↓
Publish Official State
This makes it easier to support:
It also creates a cleaner path from MVP to a multi-discipline platform.
A mature phygital platform can produce more than a final score.
It can capture:
This data creates value for organisers, teams and commercial partners.
One useful architecture for a multi-participant phygital platform looks like this:
The key architectural principle is simple:
The experience can have many clients, but the competition needs one authoritative state.
The tournament has only one commercial model.
Sports organisations can use phygital experiences to turn spectators into participants.
Examples include:
AR can make these experiences more interactive by connecting digital content to the physical venue. Fans could use their phones or compatible devices to discover virtual content, complete challenges, access live information or interact with branded experiences. An augmented reality development company can help translate these concepts into venue-based AR experiences while connecting them with the wider mobile, data and engagement platform.
Sports technology companies are also combining mobile, immersive experiences, real-time data and fan engagement into connected ecosystems.
A phygital environment can connect simulated scenarios with physical practice.
For example:
Digital drill → physical execution → performance data → feedback
The value is not the headset.
The value is the closed feedback loop.
Phygital experiences create more measurable sponsor interactions than passive signage.
A sponsor could own:
This also creates measurable interaction data.
Deloitte has highlighted how digital fan engagement and data can create new opportunities around attendance, engagement and sponsorship value.
Connected cycling, smart equipment and sensor-enabled training can turn physical activity into a dynamic digital experience.
This expands the category beyond elite competitions.
Phygital programmes can give schools and clubs another way to make participation more interactive.
The World Phygital Community says its ecosystem includes clubs, universities, colleges, schools and other organisations, while recent WPC material highlights youth participation and school programmes as part of the broader movement.
A modern venue can become a technology platform rather than simply a place where an event happens.
That can include:
EPAM and Infosys both describe the convergence of IoT, immersive technologies, digital products and venue operations as part of the evolving “stadium of the future.”
The wrong starting point is:
“Which immersive technology should we use?”
The better starting point is:
“What competitive or business problem becomes possible because physical and digital activity are connected?”
Write the rule in one sentence.
For example:
Teams complete a digital stage first, and the resulting score carries into a physical stage.
Then define:
Step 2: Map the physical-to-digital data
Before you get anywhere near choosing devices, build a data dictionary first.
For every event, define:
| Data point | Source | Frequency | Required accuracy | Business use |
|---|---|---|---|---|
| Player identity | App / account | Session | High | Match integrity |
| Score event | Game / referee | Event-based | Critical | Final result |
| Position | Sensor / vision | Real-time | Sport-dependent | Tracking |
| Device state | IoT gateway | Periodic / event | High | Reliability |
| Match state | Scoring engine | Real-time | Critical | Participant + broadcast |
| Fan interaction | Mobile / web | Event-based | Medium | Engagement |
This prevents teams from collecting data merely because the device makes it possible.
A practical decision framework:
| Requirement | Most relevant technology |
|---|---|
| Digital gameplay | Game engine / game platform |
| Physical telemetry | IoT / sensors |
| Visual overlays | AR |
| Immersive simulation | VR |
| Movement analysis | Computer vision / motion tracking |
| Participant interaction | Mobile / web |
| Live event state | Real-time backend |
| Historical reporting | Data platform |
| Rules and official scores | Dedicated rules engine |
The best implementation is often the smallest technology combination that reliably delivers the intended experience.
Instead of developing the full platform first, prototype one complete interaction:
Athlete action → data capture → score calculation → live update → audience feedback
That prototype reveals the real engineering constraints much earlier.
Do not test only the happy path.
Simulate:
A phygital system shouldn’t depend on every device working perfectly because real events are unpredictable, and the system needs to keep working even when something goes wrong.
A sensible progression is:
Phase 1: one sport, one venue, one device model
Phase 2: multiple matches and operator tools
Phase 3: analytics, fan engagement, and sponsor modules
Phase 4: multi-venue / multi-sport platform
Phase 5: advanced immersive and computer-vision capabilities
This reduces unnecessary upfront complexity. A product development company can help turn the initial competition mechanic into an MVP, validate the architecture, coordinate integrations and establish a roadmap for scaling the platform as the product gains users and venues.
There is no single correct technology strategy.
| Approach | Best suited to | Advantage 3 | Trade-off |
|---|---|---|---|
| Build from scratch | New proprietary sport or platform | Maximum control | Highest engineering responsibility |
| Use existing game technology | Established digital game format | Faster digital competition layer | Platform dependency |
| Integrate specialist hardware | Sensor-rich experiences | Better physical telemetry | Hardware and support complexity |
| Buy specialist components | Standard capabilities | Faster implementation | Less differentiation |
| Hybrid approach | Most enterprise projects | Balances speed and control | Requires good integration architecture |
For many organisations, the hybrid option is practical.
Keep the proprietary layer around:
Use proven platforms for capabilities that do not need to differentiate the product.
Two apparently similar phygital projects can have completely different technical scopes, so no honest quote comes without a scoping conversation. But budgeting shouldn't start from zero. The table below gives indicative investment ranges by stage. They are directional and exclude hardware procurement, venue installation and third-party licences.
| Stage | Typical scope | Indicative investment | Typical timeline |
|---|---|---|---|
| Proof of concept | One competitive mechanic, one device class, one end-to-end moment (action → score → live update), basic operator view | $10,000 – $30,000 | 6–10 weeks |
| MVP | One discipline, one venue, participant app, operator console, rules and scoring engine, live leaderboard, audit log | $30,000 – $100,000 | 4–6 months |
| Multi-match / multi-venue platform | Multiple disciplines, device provisioning, analytics, sponsor and fan modules, broadcast overlays | $100,000 – $200,000 | 6–10 months |
| Enterprise / advanced immersive | Custom hardware integration, computer vision, AR/VR, multi-region operations, live-ops support | $200,000+ | 10+ months |
| Cost driver | Why it changes the budget |
|---|---|
| Number of disciplines | More rules, workflows and scoring variants |
| Hardware | Devices, sensors, gateways and installation |
| Real-time architecture | More demanding infrastructure and testing |
| AR/VR | 3D assets, device support and performance optimisation |
| Computer vision | Data, model development, compute and calibration |
| Game integration | APIs, SDKs and platform restrictions |
| Mobile apps | Participant, fan and operator experiences |
| Venue integration | Screens, networking and operational interfaces |
| Broadcast | Overlays, feeds, content and synchronisation |
| Security | Identity, device security and access controls |
| Live operations | Monitoring, support and incident response |
| Analytics | Event pipelines, data warehouse and dashboards |
A more useful budgeting split than a generic "app development price" is: Experience + Hardware + Integration + Real-time platform + Operations
Build cost is only part of the picture. Plan for these ongoing costs from the start:
The commercial model depends on who owns the platform.
Potential value areas include:
Potential value areas include:
The opportunity may be the platform itself:
Phygital experiences can be used as campaign infrastructure.
A physical interaction can trigger a digital experience, which then creates measurable engagement.
That same principle can connect:
Product → Venue → Fan → App → Content → Commerce
The most valuable systems are therefore not necessarily the most visually impressive.
They are the ones that create a measurable loop.
The more physical and digital systems interact, the larger the operational surface becomes.
A phygital platform needs a clear source of truth for every competition-critical event.
Use:
The platform may process:
Data collection should be proportional to the experience.
A platform should not collect sensitive information simply because a device can provide it.
For UK and European deployments, data protection design should be treated as part of the product architecture, not as a policy document added later.
AI can be useful for:
But AI should not automatically control competition-critical decisions without appropriate validation and governance.
Where AI is used, teams can use the NIST AI Risk Management Framework as one useful governance reference for risk identification, evaluation, and management. NIST describes the framework as a voluntary resource for organisations designing, deploying, and evaluating AI systems.
Every event should have a fallback.
Ask:
“What happens if the internet disappears for 30 seconds?”
Good answers might include:
Bad answers are:
AWS's IoT architecture documentation demonstrates why device communication and state-management patterns matter when connected devices are not continuously available.
Immersive technology should not become a barrier to participation.
Consider:
A strong phygital platform gives the business more ways to participate rather than narrowing the audience to people who own a specific device.
This is an important question because phygital technology can be attractive before it is commercially justified.
Avoid building a full phygital platform when:
In some cases, a conventional sports app, connected-fitness product or AR experience will solve the business problem more simply.
Phygital should be an experience strategy, not a technology checkbox.
A strong vendor should be able to answer questions across product, engineering and operations.
The key distinction is between a company that can build an immersive demo and a technology partner that can operate a real digital-physical product.
A phygital sports platform sits at the intersection of several disciplines:
Product strategy + mobile + immersive technology + IoT + real-time systems + cloud + analytics
That's why phygital sports are fundamentally an integration challenge. The individual technologies matter, but the hard part is making them work together reliably across participants, devices, venues and audiences.
Designoweb is a Product Engineering and Digital Transformation Partner with 150+ professionals and 1,000+ successful solutions delivered across 25+ industries. Our teams bring together capabilities across immersive experiences, AR/VR, IoT, mobile, cloud, and product engineering, capabilities that map directly to the technology layers of a phygital sports platform.
We haven't yet built a phygital sports competition, and we don't pretend otherwise. What we have built are products that solve many of the same underlying engineering challenges: connecting physical and digital experiences, integrating multiple technologies, supporting real-time interactions, and building systems designed for real-world use.
A sports organisation does not need to launch with ten disciplines, a metaverse and a warehouse full of hardware.
A practical first release could contain:
Once that works reliably, additional technologies can be justified by evidence rather than enthusiasm.
The most interesting future of phygital sports may not be “more VR.”
It may be better for interoperability.
As sports systems become more connected, the value will increasingly come from how well different layers work together:
The evolution of the category is already moving in this direction.
You can already see this playing out. At the 2026 Games of the Future, organisers put phygital competition alongside esports and other technology-driven disciplines, and behind the scenes, the ecosystem keeps growing: new ranking systems, qualification pathways, broadcast infrastructure, community programmes. Pulling all of that into one coherent system is the hard part that's still ahead.
The technical challenge will be turning those individual capabilities into one coherent system.
That is where product architecture matters.
The strongest phygital experiences will not feel like a collection of technologies.
They will feel like one sport.
Phygital sports are not interesting simply because they combine two technologies.
They are interesting because they change the definition of the product.
The product is no longer just a game, an app, a wearable or an event.
It is the system connecting all of them.
For sports organisations and technology buyers, the opportunity is therefore less about asking, “How immersive can we make it?”
The better question is:
““What physical and digital interactions would create a better sport—and what technology is actually required to make that experience reliable?””
That is the question that should shape the architecture, budget and roadmap.
Designoweb can help turn a phygital concept into a connected digital product across immersive experiences, mobile applications, IoT integration and product engineering.
Explore Designoweb's product development services or discuss your project with the team.