Second screen and in-person play
The app was built for tables that meet online, and it works for one that meets in a room. The Dungeon Master's laptop runs the table, a television shows the board, and each player's phone is their sheet and dice.
The table view
Every campaign has a chrome-free view at /campaigns/<id>/table on the server: the board, the scene art, the sky, title cards and the initiative rail, with no panels, no message box and nothing the DM would not want seen. Open it in a browser on the television, or cast the tab. It follows the fight in real time.
The desktop app's second screen
On a desktop with two displays, the campaign's menu offers open the table on a second screen: a window with the table view, placed on the display the app is not on, full screen. Close it from that window or from the menu.
Transcription
At a human-DM table with a speech-to-text backend on the server, transcription (off by default, a campaign setting) listens to the room through the DM's microphone and feeds what it hears to the beat drafter and the chapter summaries, so the archive of an in-person session writes itself. It needs the server's push-to-talk backend; a device world has none unless its owner set one up.
Physical dice
Players choose typed entry or a Pixels die per shape; a request for a physical roll parks the turn until it arrives. The DM's own rolls can be DM-only or blind. See Dice.
Phones at the table
If the table is hosted from the desktop app, Share on this Wi-Fi lets every phone in the room join at a local address with no internet at all. Each player joins the campaign from the Android app or a browser on their phone: the Party tab is their sheet, the Hand is their turn, the Map tab is their view of the board with their own fog. Voice chat is unnecessary in a room and can be left off in the campaign settings.
Interface scale
Account settings has an interface scale for a screen seen from across a room, and the table view respects reduced motion and low effects for a television that struggles.