Kiosk Mode is a special operating mode of a digital device (tablet, terminal, computer) in which the user is restricted to a single application or service and has no access to the system functions of the device.

Systems of this kind are used in:

• payment terminals
• information stands
• electronic queue systems
• educational devices
• industrial control panels

The essence of kiosk mode

From a technical standpoint, kiosk mode is a form of hardware and software isolation of the user interface, in which:

• a single main application is launched
• access to the system is blocked
• the user's actions are restricted
• the device performs a narrow function

This turns a general-purpose device (a tablet, for example) into a specialized terminal.

An ATM is a specialized device that:

• runs banking software only

• blocks any system functions (HOME, BACK, OS settings)

• restricts access to the file system and to the internet

• ensures the security of transactions

In other words, an ATM is the classic example of a hardware kiosk.

How an ATM differs from a tablet kiosk

• A tablet in kiosk mode can run one website or one application.

• An ATM is always embedded software with hardware protection, completely closed.

• On a tablet the restriction can be circumvented through system bugs; on an ATM this is almost impossible without physically breaking in.

The history of kiosk mode

1970s – 1980s

• The first ATMs (1970s) were highly specialized and physically restricted.

1980s – 1990s

• the first information terminals in museums and airports

• specialized computers with restricted software

• Since the 1990s, the terminal kiosk approach has been used for ATMs: a single system, fullscreen, protected access.

2000s

• the growth of internet kiosks

• the appearance of full-screen browser modes

2010s

• the spread of tablets

• the appearance of mobile operating systems with kiosk mode support

• the adoption of corporate MDM systems

2020s

• cloud management

• IoT terminals

• digital panels and smart kiosks

• Today's ATMs are full-fledged kiosk systems with banking-grade security, a camera, a microphone and other sensors and devices

The purpose of kiosk mode

The main goals of using it:

1. Security

• protecting the system against unauthorized access

• preventing settings from being changed

• protecting data

2. Manageability

• centralized device management

• remote content updates

• control over user behavior

3. Simplifying the interface

• only the buttons that are needed

• no superfluous functions

• minimizing user errors

4. Business objectives

• self-service terminals

• advertising and digital signage

• POS systems

The architecture of kiosk systems

A typical architecture includes:

User
↓
Interface (UI)
↓
Kiosk application
↓
OS (Android / Windows / Linux)
↓
Hardware device

On Android, kiosk mode is implemented through:

• Lock Task Mode

• Device Owner

• MDM systems
  for example: Android Enterprise

Implementation features

1. Restricting the system

• blocking the HOME and BACK buttons
• disabling the notification panel
• prohibiting the installation of applications

2. Restricting content

• access to a single website only
• URL whitelists
• traffic filtering

3. Automation

• automatic startup when the device is powered on
• restarting the application after a failure
• content updates

4. Additional functions

• brightness control
• battery monitoring
• motion sensor
• camera control
• remote control

Examples of ready-made software solutions

In practice, specialized applications are widely used:

• Fully Kiosk Browser

• SureLock Kiosk Lockdown

• Kiosk Browser Lockdown

Problems and limitations

Despite its advantages, kiosk mode has a number of problems:

1. Attempts to bypass the protection

• users may find ways to exit the mode
• OS vulnerabilities

2. Hardware reliability

• devices overheating
• wear of the touchscreen
• power failures

3. Network problems

• loss of connection
• slow content loading

4. Maintenance

• the need for remote administration
• updates and monitoring

5. Deployment cost

• licenses
• software development
• maintenance

Prospects for development

In the coming years, kiosk mode will develop in the direction of:

• integration with AI (face recognition, voice)

• fully cloud-based management

• IoT ecosystems

• personalized interfaces

• stronger cybersecurity

Practice Ways of implementing kiosk mode

Ways of implementing kiosk mode

1) restrict the browser through its settings – a kiosk with cut-down functionality
2) write a kiosk application from scratch (with access to system functions)
3) install a demo version and then buy a license for a ready-made kiosk application
4) buy a tablet with a special Android Enterprise OS

On an Android tablet you can set up kiosk mode so that only the browser starts and only one website opens. There are several ways to do this – from the simple to the professional.

1. The simplest way – Screen Pinning

Suitable when you need to restrict the user quickly.

How to do it:

1. Open the browser (Chrome, for example)

2. Go to the website you need

3. Enable:

   • Settings → Security → Screen pinning

4. Open the list of applications → tap the pin icon

Now the user will not be able to leave the browser without a PIN or password.

Drawbacks:

• a tab can be switched

• another address can be entered

• there is no complete protection

2. True Kiosk Mode through dedicated applications

The best option when a full-fledged kiosk is needed.

Popular applications:

1. Fully Kiosk Browser

• built specifically for kiosks

• a single URL can be set

• blocks the back/home buttons

• starts automatically when the device is powered on

• password protection

Functions:

• automatic startup when the tablet is powered on

• hiding the system panel

• blocking navigation to other websites

• disabling gestures

2. Kiosk Browser Lockdown

• also produces a restricted browser

• supports a whitelist of websites

• administrator password

3. SureLock Kiosk Lockdown

• professional grade

• suitable for businesses, schools and terminals

3. Through Android Enterprise (the most correct way)

For a tablet used in a business or a project.

What is used:

• Android Enterprise

• MDM systems (Hexnode, Scalefusion and others)

What you can do:

• block EVERYTHING except one application

• prohibit settings and notifications

• set a single website

• manage the device remotely

A recommendation, if what you want is:

A mini guide

The simplest kiosk:

1. Install Fully Kiosk Browser

2. Open the settings

3. Specify:

   • Start URL (the site you need)

   • Kiosk Mode = ON

   • Auto Start on Boot = ON

4. Set an administrator password

That is all — the tablet becomes a terminal showing a single site.

What you can realistically build yourself in Unity for a kiosk application

You can build a kiosk application in Unity with an embedded browser (WebView):

Basic features — feasible

• fullscreen mode
• loading a single URL
• UI locking (the back button, swipes inside the application)
• automatic start of the scene
• hiding the cursor and the interface
• reloading the page on a timer

The following plugins are used for this:

• UniWebView
• 3D WebView for Android

What is difficult or almost impossible in Unity

Here are the key Fully Kiosk features that are hard to implement in Unity:

1. True kiosk mode (lock task mode)

This is the Android system level:

• locking the HOME button
• preventing the user from leaving the application
• blocking the notification panel

This is done through the Android API (Device Owner), and Unity cannot do it on its own

2. Automatic launch when the device is powered on

In Unity you cannot simply do this:

• a BroadcastReceiver in Android Java is required

• or MDM/Device Owner

3. Blocking system gestures and buttons

Unity does not control:

• the notification shade

• the Android system buttons

• system navigation

4. Password protection against exiting

In Unity you can implement a UI password,
but the user will still be able to press HOME without a system lock task

Architecture of a custom-built kiosk application

If you still want to build it in Unity, the correct approach is as follows:

Unity (UI + WebView)
+
Native Android layer (Java/Kotlin)
+
Device Owner / Lock Task Mode

That is:

• part of the logic in Unity

• part in native Android code

Comparison: Unity vs Fully Kiosk

Unity is suitable if:

• it is part of your project or game
• you need a custom interface on top of the site
• you need 3D or visual elements

Fully Kiosk is better if:

• you need a real terminal or kiosk
• protection against exiting matters
• you need it quickly and reliably

Conclusion

Kiosk mode is an important tool of digital transformation, making it possible to:

• turn ordinary devices into specialized terminals
• improve security and manageability
• simplify the user's interaction with the system

Despite the technical difficulties and the security concerns, kiosk mode remains a key technology for automating customer service and digital services.

See also

• Super app
• super app
• Single-page application
• single page app SPA
• MDM systems
• Progressive Web Apps (PWA)