Build with Synergy OS
A real-world signal.
Your next game mechanic.
Synergy OS provides a player signal about device energy, shared with permission. Your game decides how to respond.
How it fits together
Synergy OS provides the signal.
You design the experience.
-
Energy information from the player's device
ThingsApp reads where the electricity powering the device comes from.
-
Synergy Status from ThingsApp
The device gets a verified tier: Green, 1.5°C aligned, Not green or Not verified.
-
A permission-based connection
The player approves Synergy Login (OAuth 2.0 + PKCE). You receive the tier, never their identity.
-
Your game's response
You decide what the status changes, and what every player gets by default.
Ideas to build on
One signal.
Many possibilities.
These are design ideas; the right mechanic depends on your game.
-
Reward
Add bonus XP or a score multiplier.
-
Progression
Open an optional path through the experience.
-
Challenge
Give players another goal to explore.
-
Recognition
Offer a cosmetic, a badge or a title.
-
Access
Unlock a clearly explained feature or round.
-
Community
Design a shared goal around participation.
Design with care
Make it meaningful
for your players.
Explain what changes and why. Think about players who cannot choose their electricity source or use a supported device. Test the mechanic with real players and measure its effect.
verified status → apply the game's chosen mechanic
status unavailable or declined → the game's default behaviour
For existing games
Add a new possibility.
Keep your game yours.
-
Register your game
Sign in to ClimateIn, open Creator Studio → Synergy Login and register a client.
Open Creator Studio -
Connect with permission
Send the player to Synergy Login. You receive a signed token with their tier — never their identity.
See the OAuth flow -
Test the experience
Check every tier, a declined permission and an unavailable status. Explain the outcome to players.
Make the benefit clear.
Keep ordinary account sign-in separate from the Synergy connection. Tell players what you request and what their status changes.
Use verified data.
A demo colour is an example, not a verified signal. Read the tier from the token and handle changes explicitly.
Ready when you are
Start with the guide.
Register when you are ready.
More reference material lives in the Umweltify documentation.