# `TryOnAvailability`

> Contract 2.0.0 · package sha256 `a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e` · generated from `configurator-runtime.d.ts` by `services/onsite-scripter/scripts/build-contract-docs.mjs`; edit the source, not this file.

Interface · `import type { TryOnAvailability } from '@holostep-configurators/runtime-client/contract';` · labs, `@experimental` · since 2.0.0 · section 16. Capture, export, AR

[`canTryOn()`](Session.canTryOn.md)'s answer for the product on screen, now. Frozen.

## Members

| Member | Kind | Summary |
| --- | --- | --- |
| <a id="available"></a>[`available`](TryOnAvailability.available.md) | property | Show a Try-on control only when true. |
| <a id="kind"></a>[`kind`](TryOnAvailability.kind.md) | property | The product's rig kind; 'other' when it has none. |
| <a id="modes"></a>[`modes`](TryOnAvailability.modes.md) | property | The modes [`tryOn()`](Session.tryOn.md) can open now: `['here', 'handoff']` when available; `['handoff']` when only this device can't (`reason: 'unsupported'`: no camera API, or the embedding page blocks the camera), so a phone can still… |
| <a id="reason"></a>[`reason?`](TryOnAvailability.reason.md) | property | Present when `available` is false. |

## Declaration

```ts
export interface TryOnAvailability {
  readonly available: boolean;
  readonly kind: TryOnKind;
  readonly modes: readonly TryOnMode[];
  readonly reason?: TryOnUnavailable;
}
```

## Generic-API test (spec 3.1)

| Rule | Result |
| --- | --- |
| 1. Neutral name | pass: `TryOnAvailability` names no product |
| 2. A precedent | not recorded: no ledger row (coverage.json) names this member or its owner |
| 3. Two apps, or labs | labs (`@experimental` at a stable path, reached through `has()` or `supports()`): it graduates when a second app uses it |
| 4. The cheaper fix first | not recorded per member (Appendix B decides it per need) |