I want to use Android Tablet to show a web page in Kiosk mode ( The user can't close the page, no address bar .. )
So is there any simple solution to do that ?
Disclaimer: I founded the opensource Webconverger Web kiosk project.
https://github.com/webconverger/android is an opensource implementation of an Android 5.0 app that does just that. You could remove the close button, but the close button simply reloads the configured homepage.
Android 5.0's screen pinning locks it all down. If you must run on older Android <5 versions, have a look at good collection of Android kiosk mode hacks.
Related
I'm creating a PWA site and I have a task to hide virtual buttons and android's status bar when the PWA application is open, so that there is no way to exit the application except with the built-in "Exit" button.
I found quite an old resource about "kiosk_enabled" and "kiosk_only" in manifest.json but it doesn't work in the current (85) version of Google chrome (status bar and virtual buttons are not hidden).
developers.google.com/web/shows/google-io/2014/unleash-the-power-of-kiosk-apps
Is this functionality still working , and if so, how can I properly enable it in PWA?
At the moment (11.09.2020) implementation of kiosk_enabled in new PWA is only planned, as mentioned in these links:
Chromium blog
Fugu Request: Kiosk Support
So personally I see only the option to use special software.
For example:
Fully Kiosk Browser & App Lockdown
Scalefusion
Android kiosk
(Not for advertising purposes)
I am developing a PWA for which I want to have "add to home screen" (a2hs) functionality in standalone display mode.
During development, my PWA is running on a server which is accessible from within my local network only (not from outer internet).
When testing a2hs on Chrome for Android, I encounter the following strange behavior.
Simple add to home screen
When my PWA is added to the home screen as a normal shortcut, then everything works fine. Clicking on the shortcut will open the PWA in standalone display mode (without Chrome UI visible).
Advanced add to home screen (WebAPK)
When the PWA is added to the home screen as a WebAPK shortcut, then the standalone flag in my web manifest is ignored. Clicking on the shortcut will open the PWA within a browser tab (with Chrome UI visible).
What could be the reason of this incorrect behavior? My guess is that Google's servers need to be able to access my PWA's manifest in order to properly assemble the WebAPK. Since my manifest is not accessible from internet, the WebAPK is not correctly assembled. This is just guessing though. Can someone confirm or describe the reason for this strange behavior?
If you are using a custom port, try using the default port.
Others have reported the same odd behaviour.
This issue was fixed by using the default port.
PWA deployed in node.js running in Standalone mode on Android and iOS
Your PWA can be in complete private network(we have one) and still work as an installable (WebAPK) PWA.
Only reason you would be seeing the Chrome UI is, one of the PWA criteria is not met.
Run lighthouse report and make sure everything under PWA is passed. Post your audit report if you need help with it.
I have a Chrome Home-screen app on my Pixel-C tablet (where I have clicked 'Add to Home Screen' from Chrome Android).
Is it possible to root the Android tablet so that it automatically runs this web app in full screen mode on start-up without any user interaction being necessary? Very much like a Kiosk app, where the user should only be able to interact with the app itself (not the OS).
So far, I have tried using the Android Auto Start app, although it cannot detect Chrome Home-screen apps. My current setup is using the 'Immersive Mode' app to remove the navigation and status bar controls and then opening the kiosk style app manually.
I am open to any suggestions -- including rooting the device, which is probably necessary given the amount of control required.
You have to crate a custom launcher(Google "creating android custom launcher" for more such examples). Launcher is the home screen interface which user interacts to. In your custom launcher, you can restrict what app icons to show and what not to. You can choose this to be your only app and open it on boot and even relaunch when tried to exit.
I have created an "app/shortcut" (I don't know how else to call it) through the Chrome App on an Android tablet.
To ship this tablet to our customers, I want the tablet to be limited to only this shortcut. I don't want the entire Chrome to be opened, as I don't want to have a address bar or whatever visible; just fullscreen.
I have tried several kiosk apps and browser, but unfortunately most of them are build on Chromium, which does not support saving Passwords.
When the system is started, I want my app to be opened and don't want to give an alternative possibility.
Thanks in advance!
We have an App for a tablet with Android 2.2. This is the only App that should run on this tablet. It starts automatically.
Thats why the user should not have access to other Apps on this tablet, especially not to the settings.
How we can realize this?
You should probably write your application as a Home application. There is an example in the developer docs here:
http://developer.android.com/resources/samples/Home/index.html
Then you'd be able to switch the default Home application for your one.