Session Store

Session store is a shared realtime key-value store that is accessible by everyone in the room. Consider it as additional data associated with the session at the top level. Session store can be utilized to implement features such as pinned text, spotlight (which brings a particular peer to the center stage for everyone in the room), and more.

The session store persists throughout the session and is cleared when the last peer leaves the room.

💡 Session Store vs Peer Metadata

While peer metadata is associated with individual peers and each peer can have their own metadata, session store remains the same for every peer in the room.

How to use

Session store is only available after user joins the session. To obtain a reference to the session store, you need to override the fun onSessionStoreAvailable(sessionStore: HmsSessionStore) function of the HMSUpdateListener protocol. Once you get the reference to the store you can save it in your app for accessing later.

Setting a value for a specific key

Use the set API to assign a value to a specific key. Once a value is assigned, it will be available for other peers in the room who are observing this key.

fun updateSessionStore(data: Any?, key : String, hmsActionResultListener: HMSActionResultListener) { hmsSessionStore.set(data, key, hmsActionResultListener) }

💡 It's important to make sure the object is serializeable. Primitive types Int, Boolean etc are fine to pass and read with parsing. For a custom class, add Gson SerializedName annotations or otherwise ensure that the object can be recreated after being sent across the network. If not SerializedName, consider Keep annotations on the data classes to prevent obfuscation might be the easiest way to do this.

Retrieving a value for a specific key

Retrieve the current value and receive updates

Most of the time the application is interested not just in a current value of a key but also any updates to that value. To obtain the initial value and receive updates, use the addKeyChangeListener API. It takes a list of keys to observe and a closure that will be called for initial value and every time an update is received.

There are different ways to receive primitive values, objects and lists of objects.

sessionStore.addKeyChangeListener(listOf("time","cat","cats"), object : HMSKeyChangeListener { override fun onKeyChanged(key: String, value: JsonElement?) { when(key) { // Primitive values "time" -> { val time : Long? = value?.asLong } // Objects "cat" -> { if(value != null) val cat : Cat = Gson().fromJson(value as JsonElement, } // Lists of objects "cats" -> { val type = TypeToken.getParameterized(, if(value !=null && key == catKey) val cats: List<Cats> = Gson().fromJson(value, type) } } } }, object : HMSActionResultListener { override fun onSuccess() {/* Added successfully */} override fun onError(error: HMSException) {/* Error adding listener */} } )

You can have multiple observers running concurrently.

Managing the lifecycle of observers

During the lifecycle of the app, you may need to subscribe and unsubscribe for value updates. To unsubscribe keep a reference to the HMSKeyChangeListener:

Later when the observer is no longer needed call sessionStore.removeKeyChangeListener(keyChangeListener) API to stop receiving update.

Retrieve the current value once

Use the get(key : String, listener: HMSSessionMetadataListener) API if your application does not require updates for the key.

sessionStore.get("mykey", object : HMSSessionMetadataListener { override fun onSuccess(sessionMetadata: JsonElement?) { // Use value val data = Gson().fromJson(value, } override fun onError(error: HMSException) { // Error while retrieving } })

Limitations and workarounds in Alpha release

  • There is no permission support, which means anyone can read/write session metadata. If you want to restrict access to session metadata, you have to implement it at the app level logic.
  • Locks are required to ensure consistency of the data. If two peers update the data at the same time, it may result in a race condition where the last update overwrites the previous ones.

👀 For an example of how to implement pinned chat support using session store in an Android app with the 100ms SDK, checkout our example project.


  • Max payload size for data can be 1KB.
  • Maximum 100 keys are supported with 64KB limit applied to all keys combined.
  • Metadata size for 64 KB also include the key size.

Have a suggestion? Recommend changes ->

Was this helpful?