Problem / Current Situation

Currently, implementing real-time audio and video calling in OutSystems Reactive Web applications requires significant manual JavaScript development and knowledge of WebRTC APIs.

Developers need to manage peer connections, SDP offers and answers, ICE candidates, media streams, signaling, and connection lifecycle events.

I recently faced this challenge while implementing a one-to-one video calling feature in an OutSystems 11 Reactive Web application. I searched OutSystems Forge for a reusable WebRTC component but could not find a suitable, easy-to-use solution.

Proposed Solution

Introduce an official reusable WebRTC component for OutSystems Reactive Web applications.

The component should provide a simple visual and action-based interface so developers can implement audio and video calling without manually writing complex WebRTC JavaScript code.

Proposed Features

1. One-to-one audio and video calling.

2. Local and remote video stream management.

3. Microphone and camera on/off controls.

4. Screen sharing.

5. Incoming call notifications with Accept and Reject actions.

6. SDP offer and answer management.

7. ICE candidate handling.

8. Connection status and error handling.

9. Configurable signaling mechanism (OutSystems server actions or external signaling services).

10. Support for OutSystems 11 Reactive Web and, if feasible, ODC.

Expected Benefits

• Reduces development time.

• Makes WebRTC accessible to low-code developers.

• Avoids repetitive JavaScript implementations.

• Encourages reusable architecture.

• Enables developers to add video conferencing capabilities to business applications more easily.

Conclusion

A native WebRTC component would be a valuable addition to the OutSystems ecosystem and could help many developers build modern real-time communication applications more efficiently.