javascript-sdk-design
OvenLiveKit-Web
Our great sponsors
| javascript-sdk-design | OvenLiveKit-Web | |
|---|---|---|
| 1 | 3 | |
| 1,406 | 46 | |
| - | - | |
| 0.0 | 4.8 | |
| over 3 years ago | 2 months ago | |
| JavaScript | JavaScript | |
| GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
javascript-sdk-design
-
What are the best practices (+ hard choices) when building SDKs?
- Process pitfalls: what choices might run afoul of big companies' security processes, or create unforseen challenges in getting the integration approved outside of the code-world.
The closest article I've found is https://sdk-design.js.org/ which has some great information at the beginning and end, but is somewhat generic in the middle. I suspect theres some great info buried in one-off technical blog posts at SaaS startups as well.
Theres also the option of learning from good examples - the obvious choice here being Stripe who are known for their great documentation & SDK design https://stripe.com/docs/development
Has anyone else found themselves in this position? How did you learn and improve (without having to do it the hard way of pushing bugs to your customers production sites!)? Did you find, or create, any useful resources on building modern browser SDKs?
OvenLiveKit-Web
-
Looking for a program where I can livestream / share my screen in close to real time (like discord)
I had great luck with setting up OvenMediaEngine with a custom OvenLiveKit player HTML. I stream to the server via RTMP and it publishes the stream over WebRTC. In the best case I got around 1 second latency, since there's a bit of overhead while converting audio channels (WebRTC only supports Opus, OBS only supports AAC (I think)). Also you can't use B-Frames, so you need to pay attention to that in OBS.
-
[Use Case] The third use case of OvenMediaEngine: IoTcube Conference 2021 ( Sep 9, 2021)
We also set WebRTC as input and output by applying OvenLiveKit for Web, which can send media stream to OvenMediaEngine's WebRTC Provider to direct broadcasting using a webcam/microphone on the desktop rather than an encoder as OvenStreamEncoder, OBS, or XSplit. Well, If you are interested in OvenLiveKit for Web, click HERE for more information.
-
We have released new open-source projects.
GitHub: https://github.com/AirenSoft/OvenLiveKit-Web
What are some alternatives?
Spotify SDK - Spotify SDK | Entity and Collection oriented | Browser and Node support!
webrtc-sdk - WebRTC Simple Calling API + Mobile SDK - A simplified approach to RTCPeerConnection for mobile and web video calling apps.
hedera-sdk-js - Hedera™ Hashgraph SDK for JavaScript/TypeScript
OvenSpace - OvenSpace is Sub-Second Latency Streaming Demo Service using OvenMediaEngine, OvenPlayer, and OvenLiveKit.
Bot Builder SDK - Bot Framework provides the most comprehensive experience for building conversation applications.
OvenMediaEngine - OvenMediaEngine (OME) is a Sub-Second Latency Live Streaming Server with Large-Scale and High-Definition. #WebRTC #LLHLS
Teedy - Lightweight document management system packed with all the features you can expect from big expensive solutions
OvenPlayer - OvenPlayer is JavaScript-based LLHLS and WebRTC Player for OvenMediaEngine.
concourse.js - A JavaScript SDK for the Concourse CI API.
browser-monads - Monads for `window` and `document`
Countly - Countly is a product analytics platform that helps teams track, analyze and act-on their user actions and behaviour on mobile, web and desktop applications.