One option that I like a lot is WebSocket. It works on top TCP (and TCP+TLS) and Network framework supports it on both the client and server side. Thanks for the pointer. I did consider this at first but lack of documentation and sample code drove me away at first :D. I do have a couple of follow up questions related to this though. Currently I am using Multipeer framework. Multipeer Framework has a parameter called MCSessionSendDataMode which I have currently set to reliable. How does this help with reliability underneath? Does it make a connection using TCP instead of UDP? I am trying to understand - by moving to Network framework and using TCP as underlying framework can I have a more reliable connection compared to Multipeer? A query in the behaviour of acknowledgements - Does the send API on NWConnection throw an error if there is no acknowledgement? Does the error differ based on the underlying protocol - meaning if I use TCP I would assume the send API would throw a failure when the sending fails or when there is no acknowledgement compared to UDP where I assume we get an error only when sending fails.

@eskimo, Thanks for the response. You are correct that you shouldn’t use Multipeer Connectivity for this. Would you be saying this just because it is an overkill to use MPC here or is there any other reason? From what I currently understand, MPC can get the job done for me without me having to write a lot of low level coding that Network framework requires me to do mentioned in the link that you shared. I had ruled out Network framework for the reason that I need to be quick to market :) and MPC/CoreBluetooth offers a higher level of abstraction compared to Network framework.