Real-Time PlatformLocally verified platform build

Table-AR

A connected campaign workspace and live virtual tabletop for role-playing groups.

Built the live-play side of a two-product RPG platform: Tavern prepares characters, campaigns, and media; Table-AR turns them into synchronized sessions with maps, combat, audio, notes, and spectator-safe streaming. It is browser-based, not camera AR.

Role

Product architect and full-stack platform lead

Timeline

2023 - 2024

Users

Players, DMs, creators, and viewers

Virtual TabletopCampaign ContinuityRole-Safe SessionsLive CombatDynamic MapsSpectator Stream

Overview Architecture More Work

Live-play capability areas

Player, DM, creator, and viewer journeys

48.2%

Lighter public and login bundle graph

Connected Tavern campaign preparation to live Table-AR sessions through a short-lived, single-use sign-in handoff.

Built role-aware player, Dungeon Master, creator, and spectator journeys without exposing private game-master state.

Turned maps into playable systems with fog, vision, movement budgets, dynamic barriers, initiative, and synchronized combat.

Problem

What was broken or inefficient?

Online role-playing groups often split characters, maps, chat, music, combat, and campaign files across unrelated tools. Preparation becomes disconnected from play, while private Dungeon Master information is difficult to keep separate from players and viewers.

Solution

What Mohammed built

Tavern and Table-AR create one continuous campaign journey: prepare characters and content, launch a role-safe live table, synchronize scenes and combat, then preserve the campaign context for the next session.

Execution

What Mohammed built to move the product forward.

Single-use Tavern-to-Table-AR session handoff

Real-time join approval and role-based workspaces

Private scene preparation, fog, and player-specific vision

Dynamic movement and saving-throw barriers

Turn-based combat with synchronized health and conditions

Spectator-safe stream output with animated maps and audio

Technology signals

PixiJS scene renderingReal-time session stateRole-based authorizationSingle-use product handoffMedia synchronizationResilient state recoveryAccessible interaction patternsPerformance-aware loading

Execution Surface

Core modules and product decisions

The strongest work sits at the intersection of product judgment, technical architecture, and operating constraints.

Technology Signals

PixiJS scene renderingReal-time session stateRole-based authorizationSingle-use product handoffMedia synchronizationResilient state recoveryAccessible interaction patternsPerformance-aware loading

Connected Tavern campaign preparation to live Table-AR sessions through a short-lived, single-use sign-in handoff.

Built role-aware player, Dungeon Master, creator, and spectator journeys without exposing private game-master state.

Turned maps into playable systems with fog, vision, movement budgets, dynamic barriers, initiative, and synchronized combat.

Designed resilient media, accessibility, recovery, and performance behavior for long-running live sessions.

Single-use Tavern-to-Table-AR session handoff

Real-time join approval and role-based workspaces

Private scene preparation, fog, and player-specific vision

Dynamic movement and saving-throw barriers

Turn-based combat with synchronized health and conditions

Spectator-safe stream output with animated maps and audio

Outcomes

Unified campaign preparation and live play into one connected product journey.
Protected private DM state while supporting players and a read-only public audience.
Made complex tabletop rules feel immediate through synchronized, map-side interactions.

Lessons

Shared state is only trustworthy when every update preserves role authority and ownership.
Live products need graceful recovery, accessible controls, and performance discipline as much as real-time speed.

Recruiter Takeaway

Mohammed can turn a rules-heavy, multi-role domain into a coherent real-time platform where product judgment, system architecture, privacy, and interaction design all meet.

Architecture

How The System Holds Together

These are public-safe architecture layers: enough to show leadership judgment without exposing sensitive implementation detail.

Campaign Continuity

A single-use handoff carries identity, campaign access, characters, maps, monsters, items, and media from preparation into live play.

Authority-Aware State

Player, DM, and public views receive only the controls and information their role is allowed to use or see.

Live Scene Engine

Maps, tokens, barriers, vision, combat, animated media, and audio remain coordinated across a long-running session.