Serve Audio to SAB Apps

Scripture Apps created by Scripture App Builder are typically supplied with only one book of audio included. They then depend on the internet to download remaining audio files. MicroPi has the ability to serve audio files to Android apps generated by SAB. This feature only works when the following conditions are true:

• MicroPi is loaded with appropriate audio files from Scripture Earth.

• MicroPi's Captive Portal is enabled.

• The SAB app includes audio links in the form:

http://scriptureearth.org/data/ISO/audio/ISO-BN-BKN-CN-.mp3

• Requesting device is connected to the MicroPi's WiFi signal.

When autoloaded from Scripture Earth, the MicroPi duplicates the site's directory structure and includes a link in its website which points into this structure. The MicroPi also includes a "Captive Portal", a DNS server which redirects requests for all domains to its own internal local domain. So, when the SAB app asks the DNS server for an audio file on Scripture Earth, the captive portal redirects it into the MicroPi's mirrored SE database. The SAB app then discovers the file it requested. If the user originally downloaded the app from the MicroPi, it is logical that they return to the MicroPi to receive the audio files.

The MicroPi cannot emulate an HTTPS site. Indeed, HTTPS was specifically designed to prevent masquerading sites. This matters because SE is an HTTPS site, but includes a redirector which redirects requests to the HTTP URL to HTTPS. So, apps can still ask the real SE.org for HTTP and successfully receive the audio, but if they want this feature to work from the MicroPi, it is important for builders of SAB apps to make audio links in the form of HTTP and not HTTPS.