The app for a deployment you already use

The shard, live

The same feed the website shows, on a phone. Every one of these appears only when the deployment runs a game module and the operator has published that surface — the visibility settings are per-feature and default to off.

• Status, and the boards

  Whether the game server is up, plus champion spawns, guilds, city governors and houses as the shard reports them.

  NeedsA game module, and the matching visibility feature

• The player marketplace

  Player-run vendors and what is on their shelves, down to a single vendor. Item names arrive as the game's own string ids and are resolved against its string table, so they read the way they read in the client.

  NeedsA game module publishing the market

• Rules, leaderboards and the spawn atlas

  The deployment's published ruleset, its points and loyalty boards, and the creature atlas — what spawns where, and what it drops.

  NeedsA game module, per feature

The site's content

News, wiki and pages, read natively rather than in a browser frame.

• News, by category

  Announcements and posts in the categories the site defines, and a link from anywhere on the web opens the matching tab rather than the top of the list.

• The wiki and the site pages

  Wiki articles and whatever pages the operator has written in the admin panel, including the ones they added to the navigation themselves.

Your account

Staff are players too — the self-service screens are role-agnostic, and an administrator sees their own characters on the same screen everybody else does.

• Signing in, including two-factor

  A native sign-in with an authenticator code or a single-use recovery code, or single sign-on handed off to the deployment's own provider in a browser tab. Trusting a device skips the code for thirty days, and that trust is revocable per device from the app.

• Your characters, vendors and houses

  Character sheets, the vendors you run and the houses you own, visible to the account they belong to and to nobody else.

  NeedsA game module

Notifications, on infrastructure the operator owns

Opt-in, per stream, and delivered without a third party — which is unusual enough to be worth spelling out.

• Self-hosted push

  Push arrives over the deployment's own ntfy server, not Firebase. The app has no Google messaging dependency at all, which is why it works on a device with no Play Services and why no notification passes through anyone else on its way to the phone.

  NeedsAn ntfy server the operator runs

• The message carries no content

  What is pushed is which stream fired and an opaque reference — never the subject, the sender or the text. The app opens the right screen and fetches the actual content over the authenticated API, so a notification sitting on a lock screen discloses nothing.

Staff work, if you are staff

Gated by role in the menu and re-checked against the database on every request, so a demoted account loses the screens immediately rather than at next sign-in.

• Moderation, support and content

  The dashboard, the moderation queue, support requests and content editing — enough to answer a report from a phone. The surfaces that would let somebody reconfigure the deployment stay on the web.

  NeedsA staff role on the deployment

It looks like the deployment it is pointed at

• The theme comes down the wire

  The palette, the type, the corner radii, the logo, the hero image and even the navigation order are read from the site's own appearance settings. Two communities running this app do not see the same app, and neither of them had to build one.