I wanted to ask others what their opinion is on which framework I should use for an app design/idea that I have. I wanted to ask first before diving into one framework and then finding out I chose the wrong one.
The app's focus is that each instance of the app (each user) will be able to connect to each other and repeat the small shared data that was started on the first phone. Think of this as literally a daisy chain. The scenario would be as follows:
User A initiates a broadcast > User B connects and receives the data file or stream from User A > User C connects to User B and therefore the range would be extended, etc. The idea is you could (cough theoretically) have way more than 10 people in the chain spread out over hundreds of feet, provided they aren't moving around too much. And I know the downsides are that each user in the chain is responsible, meaning if User B disconnects from User A, then Users C through Z are disconnected, but that's not a huge concern for me.
iOS 7's Multi Peer Connectivity framework seems to be the best bet at first, however it appears to be a combo of either WiFi and or Bluetooth. I do not want users to be on WiFi for this to work (must be on same LAN I read), I would like it to be Bluetooth only, which I understand you cannot set specifically for the Multi Peer Connectivity framework.
That leads me to believe the only way (even possible?) to do what I've described above is to use the Core Bluetooth framework, but wasn't sure and wanted to see what others thought.
TLDR: Basically each user running the app acts as both a peer and an advertiser (if that's possible) and the app's focus is to be a daisy chain repeating the data/file for a long range the more users there are.
Sorry for the long-winded post in advance.
Thank you for your time reading if you got this far
The app's focus is that each instance of the app (each user) will be able to connect to each other and repeat the small shared data that was started on the first phone. Think of this as literally a daisy chain. The scenario would be as follows:
User A initiates a broadcast > User B connects and receives the data file or stream from User A > User C connects to User B and therefore the range would be extended, etc. The idea is you could (cough theoretically) have way more than 10 people in the chain spread out over hundreds of feet, provided they aren't moving around too much. And I know the downsides are that each user in the chain is responsible, meaning if User B disconnects from User A, then Users C through Z are disconnected, but that's not a huge concern for me.
iOS 7's Multi Peer Connectivity framework seems to be the best bet at first, however it appears to be a combo of either WiFi and or Bluetooth. I do not want users to be on WiFi for this to work (must be on same LAN I read), I would like it to be Bluetooth only, which I understand you cannot set specifically for the Multi Peer Connectivity framework.
That leads me to believe the only way (even possible?) to do what I've described above is to use the Core Bluetooth framework, but wasn't sure and wanted to see what others thought.
TLDR: Basically each user running the app acts as both a peer and an advertiser (if that's possible) and the app's focus is to be a daisy chain repeating the data/file for a long range the more users there are.
Sorry for the long-winded post in advance.
Thank you for your time reading if you got this far