Are there any functional or performance limitations while using the Plivo Browser SDK on mobile browsers?

We have tested our BrowserSDK on mobile browsers and documented functional limitations and performance-related aspects in this FAQ to help you implement nuanced workflows and plan resources needed by your apps. 

Our BrowserSDK supports most of the functionality available in these mobile browsers (Chrome, Firefox, and Safari), but there may be some functionality that differs between the browsers. The table below highlights these differences:

Functional

Browser Chrome Firefox Safari
Make and receive calls Supported Supported Supported
Mute and unmute Supported Supported Supported
Support for DTMF Supported Supported Supported
Call-quality metrics tracking Supported Supported Not supported
Microphone and speaker toggling Supported Not Supported Not Supported
Move browser to background during ongoing call Call continues Call continues Call continues
Receive incoming call when browser is in background Rings only when the browser is brought to the foreground and then the call can be answered as usual. Rings only when the browser is brought to the foreground and then the call can be answered as usual.
Rings only when the browser is brought to the foreground and then the call can be answered as usual.
Incoming PSTN call during ongoing SDK call Both calls happen in parallel. SDK call will be overwritten by PSTN call (audio running in background and no audio heard from app), but when PSTN call is disconnected, SDK call continues.
Both calls happen in parallel.
Echo cancellation and noise reduction Supported Supported Supported

 

Performance

While using the Plivo BrowserSDK on mobile browsers, we have analyzed the performance aspects below.  You can use this information to help you plan the resources needed in your apps. If you notice any of these performance-related behaviors different in your case, please reach out to us via our support portal

Browser Chrome Firefox Safari
CPU usage on-call Max 7%
The browser doesn’t provide this information at the Javascript library (SDK) level.
11.6%
CPU usage idle state Max 1% 1.9%
Memory consumption on-call Max 5 MB Max: 4.8 MB
Memory consumption idle state Max 3.1MB Max: 4.8 MB
Network usage Total requests: 23
Transferred over Network: 645 B
Resources loaded by the page: 1 MB
Finish: 1.55 s (async loading of objects)
Total requests: 7
Transferred over Network: 1.26 KB
Resources loaded by the page: 778.32 KB
Finish: 19.88 s (async loading of objects)
DOMContentLoaded: 121 ms
Load: 142 ms
Domains: 4
Resources: 6
Total loaded: 2.97 KB
Bytes transferred: 536 B
Time: 0
Jitter 4ms No Jitter No jitter
RTT 122ms 105.91ms,100.12ms
150.48ms, 100.28ms
Packet loss No Packet lost 0.03% (No Packet lost) No Packet lost

 

Was this article helpful?
0 out of 0 found this helpful
Didn’t find what you are looking for? Create new ticket