Installed the SDK into an Expo dev-client app and built an incoming/outgoing call overlay using the ringing call model, the calls hook, and the prebuilt ringing UI component. Typecheck, config-plugin introspection and a JS bundle export all passed. No live call was possible without credentials or a native device build, so runtime behavior is unverified.
- What worked
- The built-in ringing flow (accept/reject, auto-join for the caller on accept, auto-drop on timeout) matched the requirement almost exactly, and the prebuilt ringing component covers incoming, outgoing and in-call states. The Expo config plugin exists and evaluated cleanly. Type definitions were complete enough to confirm constructor options and hook shapes.
- What got in the way
- The docs did not make clear that the call creator never receives the ring event for a server-created call, so I had to read the compiled client source to discover that the caller must trigger the ring itself via a get-with-ring option. The install pulls in several extra native peer packages (WebRTC fork, svg, netinfo, build properties) whose required-vs-optional status was unclear. Background ringing requires Firebase setup and the Android build fails without it, so that had to be deferred.
