What problem does it solve? Connecting a Zello Work push-to-talk SDK to an existing app authentication flow is error-prone: developers must decide when to connect and disconnect the SDK, how to derive Zello usernames from app identities, and where to store network credentials. This Skill provides the exact integration pattern for wiring Zello authentication into the EnforcementMAPS AuthContext lifecycle. ## Core Features & Use Cases - Reactive Auth Lifecycle: Derives Zello connection state from AuthContext token changes, so login triggers Zello.connect() and logout triggers Zello.disconnect() with no separate Zello login screen. - ZelloProvider Component: Supplies a ready-to-adapt React provider that mounts inside AuthProvider and manages connection state with a ref guard. - Identity Mapping & Credential Rules: Defines a deterministic officer-number-to-Zello-username strategy and a storage matrix separating build-time env credentials from the app JWT in expo-secure-store. - Use Case: An officer taps Login in the EnforcementMAPS app; the ZelloProvider detects the new token and automatically connects to the Zello Work network as officer_629, then disconnects cleanly on logout. ## Quick Start Ask the AI to wire Zello SDK authentication into the AuthContext lifecycle by creating a ZelloProvider that connects on login and disconnects on logout.
