Greetings fellow developers!
I want to configure non-Apple WiFi device using iOS application. Connection would be through WiFi which is created by this same device.
1. Is it best to use Apple's WAC (Wireless Accessory Configuration) feature or is it possible to accomplish it without this? (No need for MFi license then)
2. If it is possible without using WAC: Which would be more time-consuming and expensive, developing the custom solution without WAC or the process(and cost) of getting MFi license?
3. Are there any other disadvantages to deal with if not using WAC?
The caveat here is that while configurating the app also has to access internet through cellular network to get data for configuration. Question about this matter can be found here: https://forums.developer.apple.com/thread/46528
What are your thoughts, experiences on this?
Thank You!
1. Is it best to use Apple's WAC (Wireless Accessory Configuration) feature …?
Yes. WAC is by far the best user experience here.
2. If it is possible without using WAC …
Yes. The problem is that the user experience is dire. It runs something like this:
user runs Settings to switch to your accessory’s Wi-Fi
user runs your app
user enters their home Wi-Fi settings (typically the SSID and password) into your app
your app passes them to your accessory
your accessory tries to join the home Wi-Fi
when your accessory shuts down its own AP, iOS should switch back to the home Wi-Fi
And that’s the best case scenario. If something goes wrong, like the user mistypes their password, the process can be a lot more confusing.
There are steps you can take to improve this but the reality is that it will never be as smooth as it is with WAC.
3. Are there any other disadvantages to deal with if not using WAC?
I think the above is sufficient, eh?
Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
let myEmail = "eskimo" + "1" + "@apple.com"