Enterprise IT-sponsored, customized video conferencing platform for internal collaboration.Branded service for a telehealth provider.Secure, self-hosted video meetings platform for a security expert.Casual online video chat tool for a sysadmin novice.It’s used by paying customers – Jitsi’s custodian, 8×8, uses Jitsi with its customers, many of which are critically-minded enterprises, so they have an ongoing economic incentive to keep it maintained, secure, and feature-competitive.Īs you might have inferred from the previous section, Jitsi is a big and complex project that serves many use cases.It’s easy to see its features in a production environment – anyone can try the Jitsi Meet app at any time at completely free.It has an active community – beyond the many active contributors on /jitsi, the project also has an active community board for questions and help over at.It includes many development API’s and SDKs – with multiple levels of JavaScript APIs (which we will cover), an Electron option, React and React Native SDKs, various Android and iOS SDK options, and even watchOS support, developers can modify the standard Jitsi Meet app and launch their own modified apps without needing to fully fork and modify lower-level components (which some still do).It works on many platforms – support for all major browsers native desktop apps for Windows, macOS, and Linux native mobile support for iOS and Android even some Apple watchOS support.It is 100% open-source – perhaps excepting some deployment scripts, everything you see on, is fully open-sourced somewhere in /jitsi without any proprietary modules or their own closed dependencies.There are a lot of parts to Jitsi (which we will get to), but the culmination of these pieces is a full-featured meetings application that aims to remain competitive with major meetings applications like Zoom, Google Meet, etc. There are a few drivers behind this popularity: Within WebRTC, Jitsi continues to be one of the most popular WebRTC projects. iFrame API with Jitsi-as-a-Service (JaaS)Ībout Jitsi Why is the Jitsi project so popular?.Getting more complicated with extra features.Make sure to check any Jitsi Marketplace Applications.How much of the Jitsi Meet front-end do you want to keep?.Do you need a Service Level Agreement (SLA)?. Do you need your own server infrastructure?.Let me know how well it does in that regard in the comments! This post won’t tell you everything you need to know about Jitsi, but I do expect it will help put you in the right direction. Finally, I finish with a review of the major developer options for using Jitsi as part of your app. I then take a deeper review of the 3 main infrastructure alternatives you can start with, including a step-by-step self-install guide. The post starts with some background on Jitsi and some starting considerations. The project is very active and is continuing to evolve so there is plenty more to learn. I thought I was familiar with Jitsi, but reducing all of Jitsi down into something that could be read in 10-15 minutes was harder than I expected. I agreed to put together this sponsored post so long as I could help make some sense of the large Jitsi ecosystem of projects first and position JaaS and 8×8’s other commercial services aimed at the developer community as part of that. They asked for my help introducing their new JaaS service. That’s what this post aims to help with.Īlways eager to share their work, the Jitsi team are frequent webrtcHacks authors and always happy to review the work of other authors. However, the bad side of having so many choices is navigating all the options to figure out which one to make. The good news with that approach is that Jitsi gives you a tremendous number of choices. The team, along with the larger open source community, has added a lot and deprecated relatively little over the years. In the nearly 20 years since was started, it has amassed 140 open source repositories, a huge community, a popular free meetings service, several commercial options, and now even a Communications Platform as a Service (CPaaS) with 8×8’s Jitsi as a Service (JaaS). It evolved out of SIP client software into a Selective Forwarding Unit (SFU) before evolving into a full-fledged meetings platform. Jitsi was one of the first open-source WebRTC projects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |