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!
Related
I used to be able to override a flag in Chrome to hide the default share screen, thus giving direct/one-tap access to all the apps on my phone, but the option appears to be done now with Android 10.
I guess it could be sharing from any app on my phone, not just Chrome.
Any other way to do this?
Thanks.
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've got a sticky situation. I'm developing a kiosk-style tablet application on JellyBean, and we're stuck with JellyBean.
We don't install a standard launcher on our Android tablets, and instead supply our own Home Screen/Launcher app, so that our application starts on system startup.
We were using a WebView for our GUI app. The WebView that comes with JellyBean is buggy and deficient in many ways, so our app doesn't work correctly in the WebView.
However, Chrome runs our app perfectly, so we want to switch to using Chrome, which we would launch from our own Home Screen application on startup.
We need to start it in full-screen mode, just like Launchers do when they launch any app/URL via a link that was placed on the Desktop.
I can't for the life of me find out how launchers pull this off.
I've tried adding --app="xxx", and/or --start-fullscreen to the /data/local/chrome-command-line file, but all to no avail. The additions options show up on the "chrome://version" screen in Chrome, but they have no effect.
Does anyone have any clue how they manage to launch Chrome in full-screen mode?
These tablets are all rooted tablets, completely under our own control, so no solution is out of bounds.
Thanks for any help!
I'm developing a tablet app on a Samsung Galaxy Tab 10.1 (Android 3.2). The tablet will be dedicated to running this app, which is used in an industrial environment. Our app will "own" the tablet and users can only access device features via our software. We already have a successful app like this running on phone-sized devices running Gingerbread.
On the bottom of the tablet screen Samsung has placed a "System Bar" (N.B.- NOT the Action Bar) and all kinds of other apps and widgets can be accessed from this bar. Is there any way to programmatically access this System Bar, to either modify (depopulate it of all its apps and clutter and just keep the Home and Back buttons), or to hide it altogether?
Thanks in advance.
You can hide the bar programmatically, but it requires root access to do so. This guy wrote an app to do it, and published the source code.
It is possible to remove the mini-apps, but it requires root - remove the APKs that the "mini apps" refer to, and they will disappear from the bar. There is no way to easily or programmatically do this, and your best option is to write a custom ROM with those apps removed. It's a giant pain in the ass.
If you don't need anything specifically from 3.2, then you should be able to track down a stock android 3.1 image that shipped on the galaxy Tab before touchwiz was ready. This will not have the "mini apps" or the screenshot button on the system bar. If you flash that, you won't need to root, as it's a signed image.
Im develping an app using apk 12 for 10.1 inch galaxy tablet. I would like to design a home screen only with my apps icon so that user will not be able to access anything else. Can I do that ? If yes, how ??
I would like to design a home screen only with my apps icon so that user will not be able to access anything else. Can I do that ?
Yes, it is possible to create a home screen application.
If yes, how ??
There is a Home sample app in your Android SDK installation (assuming you installed the samples from the SDK Manager). It largely boils down to having an activity with an <intent-filter> using CATEGORY_HOME.
Note that the user who installs your app will have the option of choosing between your home screen and the built-in one. Even if they make your home screen the default one, they will still be able to revert that decision by removing your app:
by booting in safe mode
via the Android SDK (e.g., adb uninstall)
by getting into Settings through notifications and the like
possibly other means
For ur knowledge lot many thing are diff for honeycomb.
For your knowledge, nothing changed in this area with Android 3.0.