Sariska provides a Dart API and easy-to-integrate SDKs for building real-time features into your applications. Easily add in-app chats, instant messaging, and other real-time functionalities to your apps.
Key Features:
Real-time messaging for in-app chats and instant messaging
Easy installation
Socket creation and management
Channel creation, joining, and leaving
Sending messages, poll votes, and message replies
Presence management (track: typing, joining and leaving users)
History management (fetching chat history and specific messages)
Installation
Step 1 : Install the Phoenix Client
With Dart
dartpubaddphoenix_wings
With Flutter
flutterpubaddphoenix_wings
Step 2 : Create Socket
Establish a WebSocket connection to the Sariska server to join channels, receive events, and send messages.
// Replace {your-token} with your actual authentication tokenlet token = {your-token};// Create PhoenixSocketOptions with the authentication tokenfinal options =PhoenixSocketOptions(params: {"token": token});// Create a PhoenixSocket instance for the Sariska WebSocket endpointfinal socket =PhoenixSocket("wss://api.sariska.io/api/v1/messaging/websocket", socketOptions: options);// Called when the connection is successfully openedsocket.onOpen( () { print("Connection opened successfully!") } )// Called when an error occurs during the connectionsocket.onError( () { print("There was an error with the connection!") } )// Called when the connection is closedsocket.onClose( () { print("Connection dropped!") } )// Initiate the connection to the socket server await socket.connect()
To disconnect the user from any previous WebSocket connections and tabs before opening a new one, set the disconnect_past_tabs parameter to true in the WebSocket connection.
Disconnect Socket
Close the WebSocket connection to the Sariska server. This will terminate all active channels and prevent further communication with the server.
// Close connection to the serverawait socket.disconnect()
Step 3 : Create Channel
Channels cannot be created directly; instead, they are created through the socket object by calling socket.channel(topic) with the topic of the channel. The topic is a string that identifies the channel, and it can be any string you like.
Channel Prefix
Each channel name starts with a prefix that determines the message serialization format and persistence behavior.
chat: Use this prefix for persisting messages to the database. This prefix requires a fixed schema and is ideal for chat applications.
final channel = socket.channel("chat:room123");
rtc: Use this prefix for scenarios where message persistence is not necessary. This prefix allows sending arbitrary JSON data, making it suitable for events in multiplayer games, IoT applications, and others.
final channel = socket.channel("rtc:room123");
sariska: Use this prefix for performance-critical applications that utilize Flatbuffers as the serialization format and do not require message persistence. This prefix provides zero-copy serialization/deserialization, significantly enhancing performance.
final channel = socket.channel("sariska:room123");
Handle Errors
When an error occurs on the channel, the onError callback is triggered. The callback receives the error information in payload, if available.
channel.onError( () =>print("There was an error!") )
Close Channel
When the channel is closed, the onClose callback is invoked. This signifies that the communication on the channel has ended and no further data can be exchanged.
channel.onClose( () =>print("Channel closed") )
Step 4 : Join and Leave Channel
To join a channel, call the join() method on the channel object. The join() method returns a promise that resolves when the client has successfully joined the channel. When sending data, you can utilize the .receive() hook to monitor the status of the outgoing push message.
// Join the Channelchannel.join() .receive("ok", ()=>print("Channel Joined")) .receive("error", ()=>print("Failed to join"))// Leave the channelchannel.leave()
Payload of message containing message details, including:
content: The message content
id: The sender's user ID
name: The sender's name
content_type: The message content type (media, emoji, text)
is_delivered: Whether the message has been delivered to the recipient
created_by: The ID of the user who sent the message
created_by_name: The name of the user who sent the message
timestamp: The message timestamp
Handle Message
Receive all events for specialized message processing prior to dispatching to channel-specific callbacks. Ensure the payload is returned, regardless of modification status.
Once you've established a connection to a channel, you can start sending messages to other connected clients. To send a message, use the push() method on the channel object.
// Send the new_vote event with the payload
channel
.push("new_message", payload)
.receive("ok", (response) {
print("Poll Vote Sent: $response");
})
.receive("error", (response) {
print("Error: $response");
});
Payload of new_message containing message details, including:
content: The message content
type: The message content type (media, emoji, text)
var pollQuestion = "What is your favorite color?";
var pollOptions = ["Red", "Blue", "Green"];
// Build the payload with the poll question, content type, and options
var payload = {
"content": pollQuestion,
"content_type": "poll",
"options": pollOptions,
};
// Send the new_vote event with the payload
channel
.push("new_vote", payload)
.receive("ok", (response) {
print("Poll Vote Sent: $response");
})
.receive("error", (response) {
print("Error: $response");
});
Payload of vote containing vote details, including:
content: The vote question
content_type: The vote content type (media, emoji, text)
options: An array of vote options
For other polls APIs, please refer toSwagger documentation
Attach Media Files to Chat Messages
Attaching media files to chat messages involves obtaining a presigned URL, uploading the file to the presigned URL, and then sending the file information to the chat server.
To obtain a presigned URL, make a POST request to the API endpoint. The request payload should be empty, and the Authorization header should contain your bearer token.
StringfetchPresignedURL(PlatformFile file) async {// Prepare headers for the API request, including the authorization tokenfinal headers = {'method':'POST','headers': {'Authorizaton':'Bearer your-token'}, };// Construct the request body with file informationfinal body = { fileName: file.name, fileType: file.extension };// Send a POST request to the Sariska API endpointfinal response =await http.post("https://api.sariska.io/api/v1/misc/get-presigned", headers, jsonEncode(body));// Handle successful responseif (response.statusCode ==200) {var body =jsonDecode(response.body);return body.presignedUrl;// Handle unsuccessful responses } else {throwException('Failed to load album'); }}
Upload the File
After obtaining the presigned URL, the file can be uploaded to the URL using the PUT method.
voidUploadFile() async {FilePickerResult file =awaitFilePicker.platform.pickFiles();// Fetch presigned URL from serverString signedUrl =awaitfetchPresignedURL(file);// Set headers for the PUT requestfinal headers = {"ACL":"public-read","Content-Disposition":"attachment" };// Send PUT request with file to presigned URLfinal response =await http.put(signedUrl, headers, file);// Handle successful responseif (response.statusCode ==200) {var body =jsonDecode(response.body);return body.presignedUrl;// Handle unsuccessful responses } else {throwException('Failed to load album'); }}awaitUploadFile(); // Call this to initiate the file upload process
Use presignedUrl to upload your files
Chat History
Retrieve the chat history using two methods:
By Subscribing to Events
Subscribe to the archived_message event to receive the last 1000 messages in reverse chronological order.
voidonArchivedMessage(dynamic payload) {if (payload["messages"] isMap<String, dynamic>) {Map<String, dynamic> messages = payload["messages"];// Process the received messagesprint("Received archived messages: $messages"); }}
To retrieve a list of messages in the chat history, trigger the archived_message event to obtain the messages. Specify the size parameter to determine the number of messages you wish to fetch, and set the offset parameter as the starting index of the messages and group_by_day to group messages by day.
To receive the total count of messages at any given time, initiate the archived_message_count trigger and subscribe to the corresponding event by listening for archived_message_count.
Retrieve any specific message from a room. It takes the room ID and message ID as parameters and sends a GET request to the Sariska API to fetch the specified message.
The Presence object facilitates real-time synchronization of presence information between the server and the client, enabling the detection of user join and leave events.
Create a Presence Instance
To establish presence synchronization, instantiate a Presence object and provide the channel to track presence lifecycle events:
var channel = socket.channel("chat:room123");var presence =Presence(channel);
State Synchronization
Utilize the presence.onSync callback to respond to state changes initiated by the server. For instance, to dynamically render the user list upon every list modification, implement the following:
The presence.onJoin and presence.onLeave callbacks allow for handling individual user join and leave events. Here is an instance:
var presence =newPresence(channel)// Detect if the user has joined for the first time or from another tab/devicepresence.onJoin((id, current, newPres) => {if(!current){print("user has entered for the first time", newPres) } else {print("user additional presence", newPres) }})// Detect if the user has left all tabs/devices, or is still presentpresence.onLeave((id, current, leftPres) => {if(current.metas.length ===0){print("user has left from all devices", leftPres) } else {print("user left from a device", leftPres) }})// Receive presence data from serverpresence.onSync(() => {print(presence.list()) // List of users })
Retrieve Presence Information
The presence.list(by:) method retrieves a list of presence information based on the local metadata state. By default, it returns the entire presence metadata. Alternatively, a listBy function can be provided to filter the metadata for each presence.
For instance, if a user is online from multiple devices, each with a metadata status of "online," but their status is set to "away" on another device, the application might prefer to display the "away" status in the UI.
The following example defines a listBy function that prioritizes the first metadata registered for each user, representing the first tab or device they used to connect:
var listBy = (id, {metas: [first, ...rest]}) => {// Increment the presence count for the user first.count = rest.length +1// Set the user ID for the presence metadata first.id = id// Return the prioritized presence metadatareturn first}// Retrieve a list of online users based on the prioritized presence metadatavar onlineUsers = presence.list(listBy)
User Typing
Send information about a user who is typing. This information can be used to update the chat interface, such as displaying a "user is typing" indicator next to the user's name.
Send User Typing Event
When a user starts typing, the following code sends a typing event to other peers.