Make the app feel like your Network
App Experience controls the identity and community language shared by the Network's web and mobile experiences. These settings help people recognise where they are and describe familiar experiences in words that belong to the community.
Changes are saved to the Network and included in live client configuration. They are separate from artwork packages: use App Experience for names, language, theme, and feature availability, then publish an asset package when the app needs new downloadable artwork.
Name the app
- App name
- The full customer-facing name for the Network app. Use the name people already recognise.
- Short name
- A compact version for places where space is limited. Keep it clear without relying on unexplained abbreviations.
- Community stream name
- The name shown for the shared stream of community moments. Choose language that feels natural to the Network.
- App theme
- The base colour and interface style used by supported Network surfaces. Choose a theme with comfortable contrast in both light and dark appearances.
Changing these values updates the Network experience but does not rename an App Store listing, change an installed launcher icon, or publish a new app binary.
Choose familiar language
The Language section lets the Network rename common concepts without changing how the platform works.
- Team and Teams
- The singular and plural labels for groups of people. A Network might use Squad and Squads, Club and Clubs, or another familiar pair.
- Playlist and Playlists
- The singular and plural labels for curated challenge collections.
- Royale
- The customer-facing name for the Network's Royale experience.
These labels flow through supported web copy and the mobile tenantExperience.terminology configuration. Stable API paths and internal identifiers do not change, so integrations should never construct an endpoint from a customer-facing label.
Shape the available experiences
Feature switches decide which community experiences the Network offers. Turning a feature off hides its supported navigation and causes protected web and API endpoints to return not found for that Network.
- Friends
- Mutual connections between people.
- Followers
- One-way following and follow requests where privacy requires approval.
- Teams
- Group profiles, membership, invitations, and shared participation.
- Leaderboards
- Network standings and progress comparisons.
- Achievements
- Milestones people can discover and unlock.
- Private chat
- Direct conversations between people.
- User-generated content
- Supported experiences where people contribute their own content.
Feature availability is a Network boundary, not a temporary visual preference. Before turning off an established experience, consider existing conversations, memberships, and the moments people may still expect to revisit.
How the app receives changes
The mobile app receives names, terminology, and feature switches in tenantExperience from the live configuration endpoint. A changed effective configuration produces a new ETag, allowing the app to revalidate and receive the update efficiently.
Web requests use the same Network settings directly. Cached screens may keep their previous labels until they refresh, while unsupported endpoints enforce a disabled feature immediately.
Review before saving
- Use names that make sense without internal context
- Keep singular and plural language consistent
- Check labels in narrow mobile layouts
- Confirm the theme remains readable in light and dark appearances
- Consider existing community content before disabling an experience
- Open the Network as an End User after saving to confirm the result feels natural
Save App Experience when the settings are ready. Publish an asset package separately when artwork should change, and use live configuration rules only for targeted client settings beyond these Network-wide choices.