Currently, we call a fixed URL and a single image is returned and displayed (the sizes are already determined) within the app. Now, we need to have two to ten images that need to rotate. Each time the webpage is called, the next image is sent. Additionally, we need the file name of an associated file name passed back which will indicate which audio to play.
The number of images can be known and configured if required.
For example, a customer’s folder www.abc.com/images/ could have the following images:
Additionally, the folder will contain audio files like this:
The code needs to return the image and the audio file name rotating to the next one each time the page is called. Again, the number of images/audio files is known and can be configured if needed.
For example, the first time that the webpage is called, image1,jpg is returned and audio1,mp3 is passed back. The next time the webpage is called, image2.jpg is displayed and audio2.mp3 is returned. And so on. When reached the highest image, return back to first.
We have control over the calling of the webpage from the app webview and we can provide the webpage to the customer.