Summary
Were there any real problems because of using default fetch and websocket API for different servers?
Expected behavior
fetch and websockets should work fine same as in web client.
Observed behavior
A native library is used for both http and websockets.
May be you have some bug tickets that were resolved after using different native clients for each server?
Hi @gentlee! We use react-native-network-client to enhance reliability, performance, and flexibility when handling network requests and websockets on mobile, especially in multi-server scenarios. You can find more details on our mobile app architecture here. Let us know if you have any follow-up questions! 
Hi @john.combs. Thank you for answering.
I checked that link and found nothing about react-native-network-client. Also, it is not obvious how it enhances reliability, performance, and flexibility - are there any issue tickets in Jira that were fixed by using these clients? Or may be some documentation that shows what exactly was fixed by using it?