Waterway Plastic mobile app and API
Challenge
Rootstack was trusted by Waterway to develop a mobile application to: Authenticate with a Waterway user API. Add devices that will automatically set a configuration on the mobile application for future connections, such as Chromecast. Be able to interact with multiple devices (pools). Interact with the pool with the ability to change: lights, valves, temperature and other settings. Create and assign schedules to outputs of the pool device.
Rootstack was trusted by Waterway to develop a mobile application to: Authenticate with a Waterway user API. Add devices that will automatically set a configuration on the mobile application for future connections, such as Chromecast. Be able to interact with multiple devices (pools). Interact with the pool with the ability to change: lights, valves, temperature and other settings. Create and assign schedules to outputs of the pool device.
Solution
Our solutions Rootstack developed a mobile application for Waterway that provides real-time communication between pool devices and the app allowing to remotely interact and control aspects such as temperature, lights, modes and valves.
Our solutions Rootstack developed a mobile application for Waterway that provides real-time communication between pool devices and the app allowing to remotely interact and control aspects such as temperature, lights, modes and valves.
Results
Its architecture is based on three main elements: Waterway API: The API is in charge of managing devices per user of Waterway. Users can create their accounts and add and configure devices to their user. Pubnub: We use Pubnub as a socket server where every time a mobile application is active, a new channel session is created. The channel is responsible for transmitting changes that happen on the mobile application or the pool device. Changes are sent using commands that interact directly with the Waterway hardware. Mobile application: The mobile application is responsible for interacting with the API and Pubnub so the pool hardware can do its job of interacting with the pool.
Its architecture is based on three main elements: Waterway API: The API is in charge of managing devices per user of Waterway. Users can create their accounts and add and configure devices to their user. Pubnub: We use Pubnub as a socket server where every time a mobile application is active, a new channel session is created. The channel is responsible for transmitting changes that happen on the mobile application or the pool device. Changes are sent using commands that interact directly with the Waterway hardware. Mobile application: The mobile application is responsible for interacting with the API and Pubnub so the pool hardware can do its job of interacting with the pool.