Mobile and tablets
This page collects what Denial already documents for the mobile shell, direct touch, and the system services that shell can use. To put Denial on a phone, see Install on a phone.
Touch on a window
On an ordinary window, direct touch reserves a compositor gesture vocabulary:
- Dragging one finger from any of its corners moves the window.
- Pinching two fingers resizes it.
- A two-finger downward swipe begun in its bottom 48 logical pixels minimizes it.
- Pinching four fingers on it inward, toward its center, closes it. Sliding four fingers across it together does not.
Three- and four-finger swipes use the same shortcut bindings as the touchpad: by default, three fingers up open the Overview, three fingers left or right switch windows, and four fingers switch workspaces.
Once a gesture is recognized, Denial cancels the application’s previous touch sequence. Those gestures are recognized at the native surface boundary, so they continue to work when an application does not understand Denial shell gestures. Touch, keyboard, and text-input state, including the built-in keyboard, are part of the compositor protocol.
Mobile shell
The explicitly selected mobile shell adds:
- a paged home grid
- app recents
- notification history
- quick settings
- a status bar
- mobile wallpaper controls
- an on-screen keyboard
- rotation controls
- edge gestures
Settings opens from the mobile home screen as a normal Denial-managed Wayland window. On the mobile shell, the Screenshot quick setting captures the full desktop without opening the region selector.
Cellular status, mobile data, SIM PIN handling, fingerprint presentation, wake gestures, and haptic feedback appear only when the corresponding hardware and system services are available.
System services the shell can use
Denial uses the host’s existing services. Optional integrations disappear or become read-only when the service or hardware is missing.
With NetworkManager and ModemManager, or with Phonewave’s dmail modem service, the mobile shell shows cellular registration, measured signal quality, and whether a data bearer is connected. When dmail runs, Denial reads it first. The Mobile data tile changes NetworkManager’s global WWAN state, or dmail’s data state. It does not create an APN or carrier profile. A primary SIM PIN prompt accepts 4–8 digits and reports remaining attempts. Unlocking the SIM never authenticates the Denial session, and device authentication does not dismiss a blocking SIM prompt. PUK recovery and multi-SIM management remain outside this interface.
Fingerprint unlock needs a lock PIN, set in Settings → Lock screen. If
fprintd reports a reader and an enrolled finger and a PIN is set, verification
starts automatically whenever the native session gate is locked, including a
--start-locked session. Password unlock remains available. The Fingerprint
Settings page appears only when a reader is present, and it asks for the lock
PIN before listing or enrolling fingers.
Phonewave’s steinerd provides automatic rotation for built-in panels.
Phonewave’s hapticd can provide optional bounded tap and fingerprint-rejection
feedback.
Custom shells
The reference desktop, including its mobile scene, is a plugin. An
alternative shell is a plugin that implements ShellApplication from
package:denial_flutter_sdk/application.dart and owns its whole UI tree.
Native Wayland ownership, resource lifetimes, authentication enforcement, and
recovery stay in Rust.