Skip to content

Ouro UI for Android v0.5.0

Latest

Choose a tag to compare

@github-actions github-actions released this 19 Nov 10:00
· 1 commit to main since this release
e38acea

An agent's consequential call now asks the person on Android instead of being refused, as it does on Windows (#22). The kit also builds on AppFunctions 1.0.0 (#21), and this is the first release whose files carry a build attestation (#20).

  • OuroConfirm.install(context, actionSet) (bot.ouro.ui.actions, platform views only, so apps without ouro-hx get it) sets confirm on each consequential action that has none. An app's own confirm is never replaced. Call it from Application.onCreate.
    • What the person sees is the composed card's confirm sheet: the action's label as a question, its description, and each prepared value under its label, then Don't and Allow. Don't is the default button.
    • App on screen: the confirmation opens at once.
    • App in the background, an AppFunction call's usual case: a high-priority notification whose tap opens the confirmation. It carries no Allow and none of the values, so the person reads them first.
    • Waiting: the call suspends until the person answers or two minutes pass (OuroConfirm.DEFAULT_TIMEOUT_MS, or your own timeoutMs). Don't, Back, tapping outside, leaving the screen and the timeout all mean no, and nothing runs. The agent gets AppFunctions' denied error with the reason.
    • No notification permission, app in the background: nothing can ask, so the call is refused with OuroNeedsPerson, whose message says why and how to fix it. On Android 13 and later the app asks the person for POST_NOTIFICATIONS, which the library's manifest declares.
    • One answer for one call: each pending confirmation has a fresh 128-bit random id. The confirmation activity isn't exported, the notification's PendingIntent is immutable and single-use, and the screen reads what to show from the pending confirmation, never from the intent, so a stale or forged intent shows and answers nothing.
    • Labels: without describe, each non-null field of the input is a row, its name as words, without idempotencyKey. Pass describe for your own labels, or to keep them when R8 renames fields.
  • An action with no confirm is still refused, so nothing consequential runs that no person agreed to. A person-only action still refuses every agent with core's typed refusal.
  • AppFunctions 1.0.0. The kit builds on androidx.appfunctions 1.0.0, released on 18 November 2026, instead of 1.0.0-rc01.
  • Attestations. release.yml attests every file a release attaches: gh attestation verify ouro-hx-0.5.0.aar --repo ourostack/ouro-ui-android.
  • The sample calls OuroConfirm.install, and its agent console shows an agent's share as asking until the person answers. It adds a button to allow notifications.

Checked on: CI only. Unit tests cover the ask, answer, timeout, permission and id rules in the JVM, and the notification, the screen and its forged and stale ids in Robolectric. On an Android 17 (API 37) emulator, an agent's share through AppFunctionManager asks the person: Allow runs it, and Don't and Back refuse it. With the app sent to the launcher, a notification asks, has no Allow and none of the values, and opens the same confirmation. The maintainer owns no Android device, so nothing here has run on real hardware yet. If you have a device and something differs, please open an issue.

Install: add maven { url = uri("https://ourostack.github.io/ouro-ui-android/maven") } to your repositories and implementation("bot.ouro.ui:ouro-hx:0.5.0"). The Maven files are also attached below.