Extensions for One-on-One Apps

At this point, you can extend your baseline in the direction your product needs most.

If you are deciding where to invest first, compare Broadcast overview with SIP interconnect.

Broadcast direction

Use broadcast when the goal is wider audience delivery, not symmetric room interaction.

For this starter path, the key takeaway is to choose the broadcast model that matches your viewer experience and operations model.

Telephony/SIP direction

Use SIP and telephony integration when your workflow must bridge browser sessions with phone or SIP endpoints.

Treat this as a roadmap decision, not a required step for the starter implementation.

AI-enhanced experiences

  • Media Processor: Discover how to capture and modify video streams.
  • Audio Connector: Learn how to access and modify raw audio from live Vonage video sessions.
  • Blog Posts: See example tutorials on how live Vonage video sessions can be improved using AI.

Production-grade reference implementation

  • You need to validate that the Vonage Video API covers your meeting scenarios (lobbies, chat, reactions, screen sharing, recordings) before investing in a full build.
  • Your team wants to benchmark performance, CI coverage, or architecture decisions against Vonage’s recommended approach.
  • You are preparing a proof of concept or customer pilot and want a customizable baseline that already matches accessibility and quality gates.

For future reference

If you want to see how similar building blocks are applied in real product scenarios, these use-case paths are a good next stop:

Wrap-up

Great work finishing the One-on-One Video Sessions learning path.

You now have a practical baseline that covers one-on-one sessions, frontend/backend handoff, and quality-focused next steps. If you want to continue with deeper core capabilities (debugging, signaling, optimization, layouts), continue with Advanced Video Core API Features.