Choose an advanced API
The basic registration already owns measurement, capture and handoff acknowledgement.
Do not add a second projection manager for the same host. Use the following APIs
when your renderer already owns the corresponding work and needs to coordinate it:
| Need | API / guide |
|---|---|
| Apply deferred native placement just before an opaque Android view returns | beforeNativeReveal, updatePlacement, isProjecting and bindProjectionPlacement; see Android placement handoff. Both callbacks default to no custom placement work. |
| Manage independent pages or modals containing multiple native controls | createWebProjectionSurface / createWebProjectionSurfaces; see the renderer guide. |
| Coordinate several fallback containers in one native transaction | createWebProjectionBatch; see batch handoff. |
| Fit an existing ownership model that surface helpers cannot express | createWebProjectionScope / createWebProjection; see low-level projection. |
| Serialize replaceable state updates and recover a lost acknowledgement | createNativeUpdateQueue; see update scheduling and recovery. |
| Implement the native bridge for a custom renderer | Snapshot-manager handle methods; see native handoff. |
These are integration choices, not additional steps to complete a normal
NativeUIProjection setup. Keep business actions, SDK interaction and application
notifications in the consuming plugin.