Can we have a full page inbox rather than a floating inbox?
Yes, full page inbox is supported with our headless library in React and Flutter. You can also change the position of your inbox and the popover list (open the notification list up for inbox placed in bottom navigation and vice versa for inbox placed in top navigation) or render notifications in a sidebar using hooks in headless library
Can a message get deleted / archived once an action is taken?
We are working on adding the functionality to delete / archive notification once it is read or some action is taken on it. We’ll also be extending this functionality for cross channel communication. So, if the same notification is sent on multiple channels and the user takes relevant action on any other channel other than inbox, we’ll disable the action in Inbox notification.
Does the communication between app and server happen over a web socket?
Real-time communication using web socket is in development. Right now, we are polling the data every 20 secs (polling time is customizable).
My website is hosted on multiple domains (for our customers), each user belongs to a client. Do I need to do separate implementation on each client? If the same user belongs to 2 clients, will they be able to see the same notification in another client when it is pushed to 1 client?
- As long as you have the same code across all your domains, there’s no need for separate implementation.
- The unique identifier for a user in inbox is subscriber_id. If you are passing the same subscriber_id in both the clients, it will be considered as the same user and the notification will be visible in both the clients. If the subscriber_id is different, it will be considered as 2 separate inboxes and hence the notifications will be unique to each client.