A Laravel package for adding real-time one-to-one and group video chat, messaging, and file sharing to web applications.
Laravel Video Chat is a package that adds real-time video calling, text messaging, and file sharing capabilities to Laravel applications. It uses WebRTC for peer-to-peer video/audio streaming and Socket.IO for signaling and real-time data synchronization, solving the need for integrated communication features without external SaaS dependencies.
Laravel developers building applications that require embedded communication features, such as social platforms, customer support systems, or collaborative tools.
It provides a self-contained, open-source alternative to commercial communication APIs, offering full control over data and infrastructure while leveraging Laravel's ecosystem for easy integration and customization.
Laravel Video Chat using Socket.IO and WebRTC
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Combines one-to-one video calls, text chat, and file sharing in a single package, using WebRTC for media and Socket.IO for real-time messaging, as detailed in the features list.
Leverages Laravel's ecosystem with auto-discovery, service providers, and migrations, making installation straightforward via Composer and Artisan commands from the README.
Includes a message request system where users must accept conversations before messaging, enhancing privacy and control as shown in the usage examples.
Offers full data control and customization under the MIT license, avoiding vendor lock-in and external API costs, with a demo project available for testing.
Currently lacks group video calls, with this feature only planned for a future version, limiting its use for multi-user conferences as noted in the 'Next Version' section.
Requires multiple steps including npm installs, separate Socket.IO server setup, and Vue component integration, which adds to development time and complexity beyond basic Laravel packages.
The README provides basic examples but lacks in-depth guides on scaling, advanced WebRTC configuration (e.g., TURN servers), or troubleshooting, and misses features like screen sharing.