Connect an environment
Create the app and verify its FCM or APNs configuration.
For mobile game studios
Operate player messaging like a core game system.
Give LiveOps, product, growth, and engineering one place to run timely player communication across iOS, Android, and every title.
Illustrative studio portfolio2 live titles
Overview
Audience
Messages
Delivery
Settings
Live workspace
Mythic Forge Studio
Devices
148kTeam members
08Environments
04Current flow
Mythic ForgeProduction ready
Skybound TacticsStaging connected
Launch checklistProvider diagnostics passed
Example data for product illustration. Not customer performance.
The message layer should understand the game layer.
PushHub is organized around apps, players, events, progression, LiveOps calendars, and delivery evidence instead of generic contact lists.
How it works
Start with one title and keep the operating model as you grow.
Register real players
Attach tokens to player identity, platform, locale, version, and game properties.
Invite the team
Give operators, developers, analysts, and administrators distinct responsibilities.
Build the rhythm
Use campaigns, triggers, templates, experiments, and reporting across the release calendar.
Capability depth without the fine-print surprise.
Current and planned capabilities are labeled directly, so teams can evaluate PushHub without confusing vision for availability.
Multi-title workspace
Manage several apps and environments without mixing player data or provider credentials.
Game-shaped audiences
Use custom properties for progression, activity, economy, and player context.
iOS and Android delivery
Operate FCM and APNs from one campaign and reporting surface.
Android SDK and engine adapters
The native Android SDK is Beta and verified on devices. Unity, Flutter, React Native, Godot, and Unreal adapters build on it and are Preview.
In the game
Useful across the whole player lifecycle.
First-week momentum
Bring new players back to an unfinished goal or newly unlocked system.
Live content
Coordinate season launches, raids, challenges, and reward windows.
Healthy return
Reach lapsed players with context instead of undifferentiated win-back blasts.
Studio speed without shared-account sprawl.
Role boundaries, scoped keys, app isolation, audit trails, and readiness checks keep operators moving without removing engineering control.
One company boundary
Teams and subscription limits are visible at workspace level.
Per-app credentials
Each game keeps separate provider configuration.
Production readiness
Provider diagnostics expose missing or invalid setup before a campaign.
Questions teams ask before they commit.
Yes. Environments can be represented as separate apps with independent credentials, devices, and campaigns.
Build the next player return.
Start with one app, one meaningful moment, and one audience worth reaching.