I have a weird problem. We have about 200 tablets in Kiosk mode at retail stores. Sometimes the inventory app gets stuck on the wrong screen, or I need to force it to open a specific URL for a promo.
Right now, my team has to remote into the screen (which is slow and creeps out the employees) just to tap a few buttons. I saw Deploy Custom intent in the hexnode actions menu but have been too scared to touch it. Is this actually useful, or just for developers?
79 Views
Dude, Intents are the best-kept secret in Android management. Stop remote controlling the screen. It’s a waste of bandwidth.
Think of an Intent as a Direct message to the app itself. Instead of you virtually tapping the screen, you tell the OS: “Hey, launch com.myapp.inventory and go straight to the SettingsActivity.”
If you know the Class name of the activity you want (ask your devs), you can create an Explicit Intent. It forces the app to jump to that specific screen instantly. No user permission needed. It’s like a command-line interface for the GUI.
Rose is right, but a word of warning: Be careful with implicit intents.
If you just send a generic open webpage command (implicit) without specifying the exact browser app, the device might pop up a ‘Which app do you want to use?’ dialog. If your device is in kiosk mode, that popup can sometimes break the lockdown or confuse the user.
Always use explicit intents (targeting the specific app package) for kiosk devices. It ensures the action happens silently in the background. We use this to force-launch our Vpn app before the user even logs in.
We actually use this for data entry, which sounds crazy but works.
You can pass Extras (little bundles of data) with the Intent. So, when we deploy a new tablet to a driver, we send an Intent that launches their route app and pre-fills their username field.
It saves them 2 minutes of typing, which adds up when you have 500 drivers. It turns the device from a dumb screen into a pre-configured tool the second they turn it on.
Don't have an account? Sign up
