HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Hi.
The change sounds reasonable, our main need is for the user to be notified that they have been sent a message without having the user continually have to make sure the app is still connected to the server.
From my perspective, they can be marked as away or even as offline, as long as when a message is sent to them they get an APNS or FCM notification, ideally it should able to be stay running in the background enough like consumer level apps. Since that is one of the things we need to compete with. Apps like Signal tick the boxes on this well, if we can similar level of notification consistency that would be really good.
No one really checks if they are online when using Signal, everyone expects messages to be delivered, and for them to get a notification of some description when they have been sent a message, That is where we need to be with Sametime. The only time a device should be offline is when there is no network connectivity for the mobile device, the server connected to is offline, or the user has purposely logged off/marked themselves offline.
Hope that makes sense.
What we are evaluating is changing the "Stay Online" to "Remain Available" with the same duration options. Once that time expires, the user would not show as available BUT can still receive messages. When in this state where the server is aware of the users mobile client device, the user will receive a notification a message was received. Selecting the notification will launch the mobile app, logging the users in as "available" to receive the message. This is aligned with many mobile applications that limit the "available" status when the mobile app has been in the background for x time. One week "available" without any activity would still be an option, but we want to notify a user a message has been received vs a session expired. Remaining "available" infinitely without ever activating the mobile client is a concern. Will the approach described meet your environment needs? In the current design, we do notify the user when the stay online has expired to simply bring the mobile app to the foreground to reset the available timer.
Do we have an ETA on when we will see this in v12?
Thank you
We are addressing this with our v12 release.