I will consider it… Managed to fix the speed issues I had with my ethernet over powerline adapters, so things are good right now. Will probably have to upgrade some time in the future.
Would never buy an iPhone though… 
But that is just me and the rest of the family. We run an Apple-free zone, except for two iPods.
Since this thread was originally about RPi 3 wireless speeds, I ran a few iperf tests with a Pi 3 about 1 metre from the router, using the default values. The packets cross between subnets, so that would have added a bit of latency. One network is gigabit and the other (192.168.11.*) is 100 Mbit.
First TCP:
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
[ 4] local 192.168.11.51 port 5001 connected with 192.168.11.4 port 60143
[ ID] Interval Transfer Bandwidth
[ 4] 0.0-10.5 sec 59.6 MBytes 47.6 Mbits/sec
[ 5] local 192.168.11.51 port 5001 connected with 192.168.11.4 port 60144
[ 5] 0.0-10.6 sec 60.2 MBytes 47.7 Mbits/sec
[ 4] local 192.168.11.51 port 5001 connected with 192.168.11.4 port 60145
[ 4] 0.0-10.5 sec 59.1 MBytes 47.3 Mbits/sec
With UDP, you need to specify the bandwidth, or it defaults to around 1 Mbit/sec. I started at 50 Mbit/sec and progressively reduced it until I was getting zero packet loss. That turned out to be at a setting of 45 Mbits/sec.
------------------------------------------------------------
Server listening on UDP port 5001
Receiving 1470 byte datagrams
UDP buffer size: 160 KByte (default)
------------------------------------------------------------
ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] local 192.168.11.51 port 5001 connected with 192.168.11.4 port 58662
[ 4] 0.0-10.0 sec 53.7 MBytes 45.0 Mbits/sec 0.378 ms 0/38314 (0%)
[ 4] 0.0-10.0 sec 1 datagrams received out-of-order
[ 3] local 192.168.11.51 port 5001 connected with 192.168.11.4 port 52999
[ 3] 0.0-10.0 sec 53.7 MBytes 45.0 Mbits/sec 0.388 ms 0/38314 (0%)
[ 3] 0.0-10.0 sec 1 datagrams received out-of-order
[ 4] local 192.168.11.51 port 5001 connected with 192.168.11.4 port 44639
[ 4] 0.0-10.0 sec 53.7 MBytes 45.0 Mbits/sec 0.371 ms 0/38314 (0%)
[ 4] 0.0-10.0 sec 1 datagrams received out-of-order
So not bad, though these figures are likely to be getting close to the Pi 3’s upper performance limit for WiFi in good conditions.
40Mbps for 1x1 single band 802.11n is the best you will get.
Good enough for 1080p, but depends on your network environment.
Would not the bandwidth needed depend a lot on the bitrate? Ie:
Video
ID : 1639 (0x667)
Menu ID : 1302 (0x516)
Format : MPEG Video
Format version : Version 2
Format profile : Main@Main
Format settings, BVOP : Yes
Format settings, Matrix : Custom
Format settings, GOP : Variable
Format settings, picture structure : Frame
Codec ID : 2
Duration : 2 h 5 min
Bit rate mode : Variable
Bit rate : 3 403 kb/s
Maximum bit rate : 6 000 kb/s
Width : 720 pixels
Height : 576 pixels
Display aspect ratio : 16:9
Active Format Description : Full frame 16:9 image
Frame rate : 25.000 FPS
Standard : PAL
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Top Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.328
Stream size : 2.98 GiB (88%)That clip is only 6Mbps maximum, so would play fine on all but the most contended or low signal 802.11n networks
Thought so and that is the bitrates I see on my recordings, but then again do we not do HD. No need at this point. Perhaps in a few years when we need to buy a new TV. When we bought this, we did an A/B test between 37" and 40" full HD and decided to use the extra 500€ to get a proper espresso machine instead