Device setup is the first thing a customer does with your product. A confusing setup flow creates returns and support calls before the product has a chance to work.
Provisioning methods
| Method | How it works | Trade-offs |
|---|---|---|
| BLE provisioning | The app connects over Bluetooth and sends Wi-Fi credentials | Best user experience, needs BLE on the device |
| SoftAP | The device creates its own Wi-Fi network for the phone to join | Works without BLE, but users must switch networks |
| QR code plus cloud | A code links the device to the user's account | Needs a backend, good for fleets |
What a good setup app does
Find the device
Scan and show only your devices, ideally with a name or code printed on the unit.
Secure the session
Encrypt the link and verify a proof of possession, such as a code on the device, before sending credentials.
Pick the network
Let the device scan for Wi-Fi networks and show the list in the app.
Confirm success
Wait until the device reports a working connection, and explain clearly if it fails.
Keep it useful
After setup, show status, settings and updates, so the app stays valuable.
Frequently asked questions
Do I need a separate iOS app?
For most consumer products, yes. Building the firmware protocol once lets both apps share it.
Can the same app update firmware?
Yes, over BLE or by triggering a network update.
Should firmware and app be built by the same team?
It helps. One protocol document and one owner remove most integration bugs.
Embedded systems consultant at TechProgeny, Bengaluru. 7+ years and 29+ shipped products across firmware, embedded Linux, edge AI, apps and IoT servers.