On the 123rd episode of Speedify LIVE we hold our weekly Office Hours in yet another Developer Takeover, hosted by our very own Brian and Kevin.  

As per usual, we answer viewer questions, discuss what’s new and what’s yet to come in Speedify, and talk about the many different ways we test Speedify to make sure it works well for everyone.

Here are our 5 takeaways from our Office Hours:

1. Speedify 12.4.1 is out, adding more bug fixes to our new and improved 12.4 version! We have recently updated our connection Priority settings to have an Automatic option which will intelligently recognize what type of connection you’re actually using and set their Priorities accordingly. 
2. The Speedify Team is working hard on making sure we support the latest versions of both Android and iOS! In-house, we’re already running Speedify on Android 13 without issues so far, but we’re working on making all the necessary tweaks to notification permissions and other smaller things to perfect how Speedify works on all devices. 
3. If you want to add more than 2 connections to Speedify you may need to purchase additional equipment! Windows and Linux are the easiest to get additional USB adapters for, while MacOS can be a bit tricky with what they support. On iOS, however, you can get a USB3 camera adapter and add as many dongles as you want and hook it up to an iPad for more connections. 
4. When it comes to ensuring that Speedify is properly tested, our QA department takes on a combined approach. Our amazing QA team manually tests every possible scenario before release, we do IRL streams to test real-life scenarios, while we also run thousands of automatic tests daily in a virtual environment to test different network types, speeds, latencies, etc. as well as any customer-reported problem as we can to make sure Speedify works well.
5. Apart from a Raspberry Pi, you can run Speedify on other development boards as well! You should be able to run Speedify on any x86 or ARM based board, as long as you run a Debian-based operating system on it. We even have some blogs about our tests, like the one we did on the Odroid board.