Do not use Persistly as a real-time multiplayer state authority.
When Not To Use Persistly
Persistly gets worse when you push it outside the save-sync boundary.
The cleanest integrations are the ones that keep Persistly focused on save persistence. If you need live multiplayer or broad backend systems, use a different stack for those concerns.
Bad Fit
These are the patterns Persistly does not try to solve.
Do not use Persistly for matchmaking, presence, or social graph products.
Do not use Persistly as a giant unbounded blob store for arbitrary game telemetry or content.
Do not assume externalUserId is a public save-discovery API in shipped clients.
Do not sync every frame. Persistly is built for meaningful lifecycle sync, not continuous gameplay replication.