Skip to content
AA-017 Production

TableSync: A Local-First Tabletop App for Phone, Desk, and Projector

TableSync is a free, local-first app for in-person tabletop games: a game master cockpit, a projected map with a grid calibrated to a true inch, and a player app on each phone. It runs with no account and no back end of its own, and its release tooling refuses to ship content that is not openly licensed.

What is TableSync?

TableSync is a free app for running in-person fifth-edition tabletop games. It gives the game master a cockpit on a laptop, puts the battle map on a projector or a flat screen with a grid that measures a true inch, and gives each player a character sheet on a phone. It has no account and no TableSync back end. I designed it, built it, and released it to Google Play, the web, and Windows as one person, and every release is cut by tooling that refuses to ship unless its checks pass.

Dungeons & Dragons and D&D are trademarks of Wizards of the Coast LLC. TableSync is independent and is not affiliated with, approved or endorsed by Wizards of the Coast.

What problem does it solve at a physical table?

A physical table runs on three surfaces that do not talk to each other: paper character sheets, the game master’s laptop, and a map that is drawn by hand or projected at the wrong scale. Miniatures have a one-inch base, so a projected grid that is not one inch per square makes every measurement at the table wrong.

TableSync starts from the constraint the room already imposes. The people are in one room, on one network, and the game master’s computer is the only server the table needs.

How do the phones and the projector stay in sync without a cloud?

The game master’s computer runs a small local server, and every other window is a browser page that talks to it. Windows on the same machine share state through the browser’s BroadcastChannel API. Phones on the network receive the same messages through a server-sent-events relay and post their own changes back to it.

Server

The server is Python 3.11 using the standard library only, with no third-party packages. It binds to the local machine by default and to the local network when the game master opens the table to players.

Browser application

The cockpit, the projector view, and the player app are plain ES-module JavaScript and CSS. There is no framework, no bundler, and no build step between the source and what the browser loads.

Android and desktop shells

The Android app is a Capacitor 6.2.2 shell around the same web bundle, published under the package id style.tablesync.player. The Windows download bundles the server with its own Python runtime, a web view, and the cloudflared tunnel client, so the game master installs nothing else.

The privacy position follows from the architecture. Character data stays on the player’s device and leaves it only when the player joins a table, when it goes to the game master’s computer. Looking up a join code sends the code alone to a small address service I run. A game master who publishes a table over the internet does so through a Cloudflare tunnel, and the Android app’s data is included in the phone’s own system backup when the owner has that enabled.

How does a projected grid measure a true inch?

The game master calibrates it once against a physical ruler. The cockpit draws a red calibration box that is ten grid cells wide, the game master holds a ruler to the projected image, and adjusts the box until it measures ten physical inches. The projector view then draws every cell at that scale.

The calibration is stored on the server with the rest of the board state, not in one browser. Every machine that opens the table agrees on the scale, and the projector is calibrated once per setup instead of once per session.

How does the release tooling keep copyrighted game content out?

Every game record carries its provenance, and the build refuses to package anything that is not openly licensed. The published app contains only System Reference Document content, which is released under CC-BY-4.0. A verifier classifies each record, and a record of copyrighted book content is reported as a leak. A leak is always fatal: the packager will not produce a release from a data tree that fails the check.

The Android build for version 1.6.2 records what that gate let through: 370 monsters, 658 spells, and 1298 items, all marked SRD-only, with nothing forbidden found in the 740 entries of the package. The application code is MIT licensed.

Publishing to Google Play works the same way. The publishing script is a dry run unless told otherwise. It refuses store text over the length limits, images of the wrong size, a bundle whose checksum does not match the recorded one, a package id other than the expected one, and a version code that is not higher than every version already on the store. It reaches the production track only when the word production is typed out in full. There is no default that publishes.

Why did five apps become one?

I had built five separate apps and it was the wrong structure. The player app, a game master app, a solo-play app, a map app, and a rules reference each had their own Android package, store listing, and release train. Only the player app ever reached production on Google Play. The other four stopped at drafts, and passing a character from one app to another needed a hand-off that a browser cannot perform between separate web apps.

The same code now ships as one app with five spaces and a switcher in the header. The merged bundle resolves to a closure of 158 modules, 266 files, and 9.92 MiB. Switching between spaces took about 285 ms from ready to finished across five measured switches on the served bundle. A hand-off between spaces is now a write to an inbox on the same device followed by a page load.

What is not finished?

Three things are open, and the project’s own documentation says so. The iOS version exists as a complete Xcode project and has never been installed on a device, because building it requires a Mac. The Windows download is a portable folder that is not code-signed. An end-user audit of the merged app is complete, and the fixes it produced are built and awaiting release.

TableSync is on Google Play, runs in a browser at undeployedadam.com/tablesync, and has a download page for the Windows build.