Android lockdown app (use Android as an advertisement screen)

Specification for Android lockdown app Purpose To lock down an android device to Chrome in order to use as an advertisement screen/DS screen. Requirements 1. Android shall always boot in “locked down” mode. 2. In “locked down” mode the device shall display Chrome in fullscreen (no toolbar) and go to a URL (the URL must be configurable in the app settings, the app settings can only be reached once correct password is entered which takes the device out of “locked down” mode). 3. The device can only go back into “normal” Android mode by entering an unlock password (the password must be configurable in the app settings which one can only reach after entering the correct password). 4. All controls are to be disabled while in “locked down” mode, so touching the screen (including all gestures android might otherwise respond to) or pressing any other button on the device (including power button, volume control etc.) shall only bring up a password prompt (and of course the android keyboard for input) to give user a chance to unlock. If correct password is not entered within a time limit (5 seconds by default but include this time limit in the app settings so we can change it later) the password prompt and keyboard shall be hidden and device go back to displaying Chrome (not reloading the page). Alternative to 4. I’m not familiar with android development but perhaps it is easier to disable all the buttons and gestures (as described above) than to tie them to a certain function (the password prompt), and only have a certain control (for example the home button) display the password prompt. Just let me know which way you prefer to do it. 5. Volume for the device can only be set when not in “locked down” mode (natural consequence of requirement 4 above). 6 (If you are unable to accomplish this item 6, your bid could still be considered, as long as you inform us that you are unable to perform requirement 6): By default Android disables the ability to start playback of a video (for example youtube video) by javascript. Android has that policy to prevent website developers from automatically triggering download of large amounts of media, a user tap is required. As you can see, user tap is not possible in our case, so we want this limitation removed so that playback of videos can be triggered by javascript. 7. In app settings, possibility to give device a name (in preparation for future features below) Build with future in mind Features that we see a future need for include (we don’t need these features yet but do not build the app in such a way that these extensions are impossible to make later on, we would rather that you prepare the app for these extensions) Touch - Enable touch (on/off switch in app settings) - Lock Chrome to only whitelisted domains (list of whitelisted domains in app settings) Remote administration - Remote configuration of settings - Remote overview of what devices are online - Remote reboot of device - Remote clearing of Chrome cache (including chrome://appcache-internals, ie. all offline application data) - Sleep time settings to be fetched from an API-route in our webapp (json returned, data can be structured as you wish/require). So this is to define time of day when device is to go into sleep (or hibernation) and when to wake up again. Also dates for longer periods of sleep. I’m not drawing out the details for this since it is not a feature we need at the moment.