Installation review flow

App installation

reviewunavailableloading

Plan ready for review. No app files or tenant settings have changed.

1. Confirm the SDK version and tenant.
2. Review consent and preserve native Google attribution.
3. Review the diff before applying it.
4. Build and test on Android and iOS devices.

A generated plan is separate from SDK installation, build validation and production activation.

This composition uses existing Banner, Button and Text components. Keep service availability, generated diff, device checks and production activation separate. A successful planning response must never display an installed or production-ready state.

The Dashboard’s authenticated organization route calls Tagbook’s planning API. Server credentials remain on the Worker. Unknown stacks, missing SDKs and existing integration files require a diagnostic rather than an empty success state. Reset the displayed plan when the user edits input or switches organization.

Reuse in the Dashboard

Use semantic tokens for the form and diff panel, an associated label for each field, a disabled submit action during loading, and a polite live region for the result. Download only the returned reviewed patch; don’t offer an automatic apply/deploy action. Use the Dashboard’s language catalogs for all copy.

The service contract and CLI belong to Tagbook, while the plan route and customer interface belong to Dashboard. Senna supplies presentation; it does not store tenants or call attribution services.