Multiple devices using same auth account for realtime: Session management & limitations?

[ErdemSenolCynapse]

We're developing an multiplatform app that uses Supabase for real-time data synchronization. Our architecture raises some questions about session management and realtime connections:

Current Setup:

• Users log in with Supabase Auth (email/password)
• Same user account accessed from multiple devices simultaneously (iPhone, iPad, Mac, Apple TV)
• Each device maintains active realtime subscriptions for data sync
• Using Swift SDK (latest version)

Key Questions:

1. Is it permissible/recommended to have multiple devices simultaneously maintaining realtime connections using the same user account?
2. Are there any session management implications or limitations we should be aware of?
3. Could multiple simultaneous sessions from different devices impact server-side session storage or auth stability?

Specific Concerns:

• Session management: Does each device create/maintain its own session?
• Session limits: Is there a maximum number of concurrent sessions per user?
• Realtime stability: Could multiple devices subscribing to the same channels cause any issues?

We want to ensure our implementation follows best practices and won't cause issues at scale. Any guidance or documentation references would be greatly appreciated.

[GaryAustin1]

I don't believe there will be any issues with multiple devices for the same user connecting to realtime. It uses the jwt to manage access, not a user session. Every device will count as a separate connection to realtime. All devices will get the same notifications neglecting any connection errors. I would expect performance to be the similar to that of the same number of connections for different users.