Overview
social.plus SDK provides a powerful real-time event system that keeps your application synchronized with live data changes. When users modify profiles, create posts, send messages, or perform other actions, these changes are instantly reflected across all connected devices.Real-time events work seamlessly with Live Objects & Collections to provide automatic UI updates without manual data fetching.
Supported Data Models
Social Features
Communities, Posts, Comments, User profiles, Follow relationships
Chat Features
Channels, Subchannels, Messages, Member activities
Event Types by Model
| Model | Available Events |
|---|---|
| Community | Created, Updated, Deleted, Joined, Left, Member management |
| Post | Created, Updated, Deleted, Approved, Flagged, Reactions |
| Comment | Created, Updated, Deleted, Flagged, Reactions |
| User | Profile updates, Follow/Unfollow activities |
| Channel | Messages, Member activities, Status changes |
| Subchannel | Thread-specific updates |
How It Works
1. Subscription Topics
Create subscription topics to define which events you want to receive:2. Event Delivery
Events are delivered through Live Objects and Collections that you’re already observing:- Automatic Updates: No manual refresh needed
- Real-time Synchronization: Changes appear instantly
- Efficient: Only subscribed events are processed
Managing Subscriptions
Subscription Limits
The SDK has a maximum limit of 20 active subscriptions per session. Manage your subscriptions carefully to stay within this limit.
Best Practices for Subscription Management
Use Higher-Level Topics
Use Higher-Level Topics
Instead of subscribing to individual posts or comments, subscribe to community-level topics with
POST_AND_COMMENT level to cover all content in that community.Subscribe on Render, Unsubscribe on Leave
Subscribe on Render, Unsubscribe on Leave
Manage subscriptions based on UI state to optimize performance and stay within limits.
Automatic Cleanup on Logout
Automatic Cleanup on Logout
All subscriptions are automatically removed when
logout() is called, helping prevent memory leaks and unwanted data consumption.