Demo app

You can use our Cloud4Wi Demo apps for iOS and Android to test Cloud4Wi before integrating the SDKs, or to test your implementation of Cloud4Wi side-by-side with a complete implementation.
The app implements all the capabilities offered by the WiFi SDK and Location SDK, providing an easy and effective way to:
  • experience the accuracy of geolocation tracking
  • verify the extreme precision and reliability of location-based events
  • experience the automatic WiFi connection on your own WiFi test network

Onboarding experience

How to get the app

iOS users:
Android users:

Getting started

To get started, you'll need a Cloud4Wi account.
  1. 1.
    Download the demo app from the app stores
  2. 2.
    Setup WiFi network. Prepare the WiFi network, configuring properly the Cloud4Wi account and your WiFi hardware. Follow exactly these instructions to make the demo app work.
  3. 3.
    Link the app to your own Cloud4Wi account, by clicking "Scan Setting QR" on the first screen of the onboarding wizard. The QR code will be provided by Cloud4Wi team.
    Note: if you don't have a Cloud4Wi account, you can continue by clicking Continue with default settings, to use the app connected to a default Cloud4wi account. You won't be able to test the app on your own WiFi network in this case.
  4. 4.
    Sign up. Enter your data on the signup screen so you can easily identify your data in the Cloud4wi dashboard for testing and troubleshooting purposes.
    You can use the "identifier" field to add any identifier that you want to match with an external system of records such as a marketing automation platform or a CRM.
  5. 5.
    Grant location permissions, by responding to the OS dialog that ask permission to use location data. Each OS and OS versions have different experiences. In order to fully experience the Location SDK tracking capabilities, you should allow the app to Always allow access to location data, even when the app is not open (background)
    For app stores compliance policy, the app cannot force users to provide location permissions in order to use the app. However, if you do not provide such permission, you won't be able to perform the functional tests that the Toolkit is designed for.
  6. 6.
    On the WiFi onboarding screen, accept the OS dialog that asks permission to connect to a suggested network. Also in this case the user interface and messages are different per each OS and OS version (see user experience)
  7. 7.
    Allow push notifications permissions. Push notifications are used to send messages in reaction to location moments.
If you correctly linked your Cloud4Wi account, and if you have connectivity, you will see your user on the Contacts page in the dashboard.
To track in the background, move more than 100 meters! Note that location updates may be delayed significantly by Android Doze Mode and App Standby, iOS Low Power Mode, or if the device has connectivity issues, low battery, or wi-fi disabled.
Test details
If there are other WiFi networks in range that are known and your device has already saved its credentials, the device might prefer those networks instead of the new secure network.
For testing purposes only, we suggest removing from your phone all the known WiFi networks.
The Demo App is pre-configured to connect only to SSID named "Secure WiFi" via WPA2 Enterprise and uses the domain name for Passpoint
When you integrate the SDK into your app, you can define your own SSID name and Passpoint parameters

Using the app

Once you have your lab correctly set up, these are the functional tests that you can run.
  1. 1.
    Create Geofences from the Compass dashboard. Enter/exit from geofences with your testing device.
    1. 1.
      You'll be able to see the location events (geo-arriving, geo-leave) on the Moments > Events page on the Cloud4wi dashboard.
    2. 2.
      You can setup a Geo Events webhook streaming out the entry/exit events to your own external system and process them for your own purposes
  2. 2.
    Enter the range of coverage of your test WiFi network and verify that your device automatically connects
    1. 1.
      You'll be able to see the location events (Arriving in location, Leaving location) on the Moments > Events page on the Cloud4wi dashboard.
    2. 2.
      You can also inspect the WiFi connection logs associated with your user in the Connection logs in the classic dashboard.
  3. 3.
    You can use Campaigns to send an email or a text message triggered by the event of Arriving at a location. Campaigns, at this time, do not have yet a trigger associated with geofencing events.
The demo app will send push notifications just after detecting any of the Moments as defined in this article.
You might not see the push notification on your phone if the mobile app is already open. You can see the list of the push notification received in the Engagement tab of the app. The list of notifications does not refresh automatically, so in order to see the latest notification, click on the setting tab and then switch back to the Engagement tab to pull the newly updated data.


To link the app to another account, or register as a new user, you need to uninstall the app and install it from scratch

Copying your user IDs

For most of the troubleshooting operations, you'll need to retrieve the identifiers of your user to then inspect the data in the Clpoud4Wi dashboard or datasets. In the app, go to the Settings page and copy the GUID value and the CustomerId value.
  • CustomerId id the id that identifies a Cloud4Wi contact. This is the same ID used for identifying contacts in the APIs, manual exports and on the dashboards
  • GUID identifies a specific device in the App Consoler for troubleshooting geofecing events
Whenever you need support from the Cloud4Wi team, make sure to copy these values and report them in the support request. You can click the 'copy' icon next to the respective values to copy them to the clipboard and easily paste them into messages.

I get an error when I sign up on the mobile app

When these errors occur, one of the following situations might apply:
  • the setting QR code scanned is not valid. The app fails to add a user on a Cloud4Wi account because it is not correctly paired

During the app setup, I get an error that says the device is unable to join the WiFi network

When the app attempts to install WPA-2 Enterprise profiles in iOS, the device attempts to connect to WiFi network immediately. If the network is not in range, you'll get an error such as the one reported in the screenshot below. The profile is installed correctly and the device will reconnect automatically to WiFi whenever in range.

When I click on the SSID I get a connection error

If you click on the SSID and do not get the prompt asking for username and password, it means that you have a valid profile on your device but the authentication fails.
Find the users of your app in the Cloud4Wi dashboard, open the user profile and inspect the troubleshooting tab to see if there are any errors.
One of the following situations might apply:
  • you misconfigured the RADIUS parameters in the HW setup
  • you don't have a valid Internet Plan assigned or it has expired
  • you don't have the right Access Point MAC address added to your Cloud4Wi account

When I click on the SSID I get a dialog asking for credentials

If you get a prompt to enter username and password after clicking on the SSID, it means that your device has not a valid WiFi profile installed for that network.
Make sure you named the test network SSID "Secure WiFi"

The device is not connecting automatically to the network

The time it takes for a device to automatically connect to the WiFi depends on many factors. It can be as fast as immediate or take a couple of minutes.
If the device does not connect at all, please make sure the SSID of your WiFi network is not hidden.
If the device attempts to connect but it fails, it is more likely a problem of authorization. Check the Internet Plan assigned to the user to make sure the user has a traffic allowance.
The device may also decide to stop attempting to associate with a network if there have been many failed attempts. Failed attempts may be caused by many situations; for example, the device might have attempted to use repeatedly al older profile installed in the device that is not longer authorized.