GuidesAPI ReferenceRelease Notes
HomeLog InHome
Guides

Follow entities - Android

The Follow entities feature lets viewers follow and unfollow entities (players, teams, properties/competitions) directly within the Blaze SDK player experience. Follow state is persisted on-device automatically, and — once activity sync is enabled and the viewer is identified — synced across the viewer's devices through Blaze.

Out of the box

Every follow/unfollow — from a tap on the follow button, or from your app calling IBlazeFollowEntitiesManager directly — is written to local storage on the device immediately. This happens for every viewer, including anonymous ones, survives app restarts, and works fully offline. No backend and no extra setup are required for this baseline behavior.

Syncing across devices

If your app has activity sync enabled and the viewer is identified (an external user ID set), those local changes also sync to Blaze and back — the same gate and pipeline used for the SDK's other user-activity signals. There's no separate follow-specific flag.

Sync is not real-time: it rides the SDK's normal periodic batch/refresh cycle, not an immediate push on every tap. A follow made on one device typically appears on another after the next sync cycle on each side, not instantly.

📘

Your app is no longer required to persist follow state itself or re-seed the SDK on every launch. IBlazeFollowEntitiesManager's setFollowedEntities/insertFollowedEntities/removeFollowedEntities are for apps that want to seed from their own backend, mirror state in their own UI, or manage follow state independent of Blaze's sync — not a requirement for basic persistence.

Components


Did this page help you?