Making Speedify Better - Give Us Your Feedback
On the 178th episode of Speedify LIVE we hold our weekly Office Hours with Speedify’s CEO and the Devs to talk about all the recent improvements and what else may be on the horizon for us!
We take viewer questions, discuss how testing Starlink 24/7 has helped improve Speedify, while we also take a look at some Mailbag questions from real Speedify users!
Here are our 5 takeaways from our Office Hours:
- Speedify doesn’t currently offer split-tunneling, but we do have a Bypass option that we’re constantly working on improving! While we work on adding more Bypass options into the UI, if you’re on desktop platforms you can also use the Speedify CLI to create a custom Bypass option for specific sites and services!
- When it comes to sharing your bonded Speedify connection from a mobile device, it’s sadly not an option by default! The built-in Hotspot and Tethering option on phones will only share your default connection, not the bonded Speedify connection, but there’s third party workarounds on Android devices if you really need it!
- While Speedify 13 is out and has already received a couple bugfix updates, we’re working on more improvements coming soon! We’re focusing on enhanced Bypass options, improvements to the UI, some performance fixes for problems users have been seeing, and making our handling of Starlink even better!
- Mailbag Question No.1 brings up an issue we see often: users connecting to servers that are too far away, affecting their speeds with Speedify. While we try to cover all areas of the world, places like Africa or South America are harder to find good servers in, so our coverage may not be as good. In this case, instead the closest, or farthest server, try something in the middle. In this case, for a user in Africa, we’d recommend servers in Southern Europe.
- Mailbag Question No.2 is an interesting one: running multiple connections into a router, then into Speedify, the app will only see it as one connection! This is because what Speedify is looking for in a device is actual adapters for each connection. You may be able to find a workaround for this with a managed switch and if your device supports VLANs.