A mobile app that supports ZipKey can range in functionality from a very simple app just used for initial setup to a feature-rich app that gives the end user a complete platform to manage their connected product's Wi-Fi connections. Outlined below are the minimum requirements for a mobile app to ZipKey-enable a connected product. Take a look at the walk-thru screens in the ZipKey DevTool sample app, which gives an example of what to show on the screen for each of these flows.
ZipKey subscriber flow - if the connected product has connected to a ZipKey hotspot, and a ZipKey ISP has the credentials for the network that the mobile app is on, the user must be given an option to have the provider provision the credentials. The screen that gives this option must include the name of the provider, the logo for the provider, and the SSID for the network for which the provider has credentials. The user should also be given an option to select a different Wi-Fi network, in case they want to put the connected product on a different Wi-Fi network.
ZipKey coverage flow - if the connected product has connected to a ZipKey hotspot, but Cirrent does not have the credentials for the network the mobile app is on, the user must be given an option to select a network and enter the pre-shared key. The user should also be shown the name and logo for the provider of the ZipKey network that the connected product joined, with an option to learn more about that ZipKey provider. We recommend that you include the 'learn more' option on the screen that you present when the onboarding is complete, so that it does not distract the user while they are in the middle of setting up the product.
Local onboarding - if the connected product is not in range of a ZipKey hotspot, the user needs to be given some alternative mechanism to configure the private network credentials. The ZipKey solution includes an implementation using softAP and an implementation using BLE, either of which could be used for local onboarding. Alternatively, if you have a different mechanism in placeTake a look at the walk-thru screens in the ZipKey DevTool sample app, which gives an example of what to show on the screen for each of these flows.already, you can continue to use that solution.
Product User Binding - The Cirrent cloud needs to know whether a connected product should be discoverable (and thus made available to users looking to setup their product) when it connects to a ZipKey hotspot. When the product is initially being set up, it is discoverable. However, if it has joined a private network, and then falls off the private network and rejoins the ZipKey hotspot, it is up to the product company to decide how this should be handled. Most apps will bind the device to the user's account in the app, so that if the product falls off the private network it is still bound to the user's account and doesn't become discoverable by other users. For some products, the app won't manage the binding, so the product takes care of it itself. See here for more details on how product user binding can be managed.