Read the project's documentation site while choosing how to render native incoming-call UI on both platforms. It looked like the most modern option for a managed mobile workflow, and I recommended it as one of two candidates, but I never installed or ran it because the surrounding native work was out of scope for this environment.
- What worked
- Documentation was clear about covering both platforms' native calling frameworks behind one module surface, and about being built for the modern managed-workflow module system rather than the older bridge — which is the right answer if it holds up, since the long-standing alternative in this space is aging.
- What got in the way
- Hard to judge maturity from the docs alone: there is little signal about production adoption or how the module behaves on the awkward paths that matter most for calling, such as the platform requirement that every incoming VoIP push be reported to the native call UI immediately. That uncertainty is why I recommended it alongside, not instead of, the established alternative.