Skip to main content

One UI 7 Android Overlay Adapter

viewcompose-overlay-oneui7-android is the explicit, Material-free Android presentation adapter for One UI roots. It composes the neutral viewcompose-overlay-android transport with ViewCompose-owned One UI Snackbar and bottom-dialog presenters. It does not add a separate setOneUi7UiContent API and does not change Android root-context construction.

Artifact and stability​

dependencies {
    implementation("com.viewcompose:viewcompose-oneui7:0.1.0-alpha02")
    implementation("com.viewcompose:viewcompose-overlay-oneui7-android:0.1.0-alpha02")
}

The explicit assembly below calls OneUi7Theme, OneUi7ThemeDefaults, and One UI components, so application source declares viewcompose-oneui7 directly. The overlay adapter keeps that module as a runtime implementation dependency and exposes only shared UI Foundation token types from its host constructor; code that constructs the host with its default token snapshot does not need to name One UI APIs.

  • Stability: Alpha.
  • Platform: Android library, minSdk 24, compileSdk 36, and Java 11 bytecode.
  • API dependencies: UI Contract and UI Foundation because AndroidOverlayHost exposes the shared overlay contracts and attribution model.
  • Implementation dependencies: Host Android, the neutral Android overlay transport, Android Renderer shape bridge, and viewcompose-oneui7. Google Material Components and AppCompat are forbidden dependencies.

API quality: AndroidOverlayHost is a Q3 root-integration API. Its canonical KDoc and compiled sample define window ownership, main-thread confinement, cleanup, token snapshot, and attribution contracts.

Explicit One UI root assembly​

One UI does not require a themed Android Context before native View construction. Applications therefore keep the neutral setUiContent host and pass an explicit overlayHostFactory that constructs this module's AndroidOverlayHost with the current OneUi7ThemeDefaults token snapshot. Feed the host's integrationAttribution back into OneUi7Theme; without the adapter, the theme reports overlay capabilities as Unsupported, and installing the adapter upgrades only the capabilities that the active root actually owns. Classpath presence alone never changes behavior.

Presenter behavior​

The adapter retains neutral Android Dialog, PopupWindow, Toast, nested render sessions, and session cleanup. It adds:

  • a queued native Snackbar with a full-height pill outline, One UI token snapshot, 24dp window margin, action target, accessibility-aware timeout, and exactly-once terminal callbacks; and
  • a bottom-gravity dialog with One UI surface geometry, scrim, system-bar handling, nested ViewCompose content, outside/back dismissal policy, and drag-handle dismissal.

The initial bottom-dialog presenter has one intrinsic expanded state. It accepts skipPartiallyExpanded for protocol compatibility but exposes no intermediate partial state, so the option cannot create behavior that the presenter does not own.

The bottom dialog applies the complete Foundation-resolved appearance snapshot on show and every changed same-key update. Container color and logical shape replace the initial One UI fallback chrome, scrim zero clears the obsolete dim flag, and navigation-bar policy distinguishes an exact color from restoring the captured platform default and Android Q+ contrast enforcement. The adapter's margin, drag handle, and gesture remain One UI-owned presentation details.

integrationAttribution reports Dialog and Popup as captured One UI content, Snackbar and modal bottom sheet as Equivalent, and Android Toast as a documented Degraded platform fallback. All root, window, callback, and cleanup work is Android-main-thread confined, and the host must not outlive its attached render root.

The generated reference is available in the viewcompose-overlay-oneui7-android API tree.

Compatibility notes​

This is the first release line for the adapter. Existing One UI roots that use only neutral Dialog, Popup, and Toast behavior remain valid. Add this artifact and the explicit host assembly only when One UI Snackbar or bottom-dialog presentation is required.

Current-checkout cleanup contract​

Unreleased cleanup attempts every owned handle or delegate even when an earlier dismissal throws. Ownership is removed before terminal callbacks; the first failure is rethrown after cleanup and later failures are suppressed. Repeated clear does not retry failed terminal callbacks, and another session remains owned. Transient presenter failure releases its active queue slot; native window teardown is attempted even if nested-session disposal fails. This contract does not promise that a failing external platform API successfully releases its resource.

The audit's two-surface failure probe released only the first surface and retained the second. The candidate attempts both and retains neither (1 to 2 attempts; 1 to 0 retained entries): improved. Four foundation cleanup regressions pass within the 854-test standalone JVM run. CompositeOverlayCleanupTest and the Android presenter suites own integration validation. Window visibility and platform failure behavior still need device acceptance; the next action is to retain these regressions and exercise native dismissal with a failing child session.

Final Gradle integration validation passes 4 owning-module test(s) with zero failures or skips. The neutral run targets CompositeOverlayCleanupTest; design-system runs include their existing presenter and host-attribution suites. This adds integration evidence to the foundation failure probe without claiming that every external platform failure or device window path is covered.