WebRTC for Mobile - Challenges and Solutions
•
3 gefällt mir•4,420 views
Running WebRTC on Mobile devices is still a challenge. There is no "one size fits all" solution. This presentation was presented by Amir Zmora at the WebRTC 2014 conference in Paris
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (16)
Ähnlich wie WebRTC for Mobile - Challenges and Solutions
Ähnlich wie WebRTC for Mobile - Challenges and Solutions (20)
Mehr von Amir Zmora
Mehr von Amir Zmora (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
WebRTC for Mobile - Challenges and Solutions
- 1. WebRTC for Mobile Challenges and Solutions 12/21/2014 1 Amir Zmora @AmirZmora
- 3. Impacting Voice & Video Quality János Balázs Vladimer Shioshvili Javier Kohen
- 4. Device Network free photos & art János Balázs
- 5. From Chrome M39 WebRTC Release Notes • Issue 3712 :- With VP8 codec, the encoder has to sometimes drop frames to maintain the bit- rate. A lot of frame-drops can look worse than scaling image down. Now we added ability to scale down frames before encoding to improve quality. • Added functionality in AGC to raise the microphone level if needed at startup. This is based on some user reports of not being able to hear others in a call… • Issue 3785 :- Fixed one way audio issue in Chrome. The problem was that NetEQ was unable to handle a big jump in timestamp. • Issue 423696 :- Fixed audio glitches on Mac when webrtc and webaudio streams are used at the same time. • Issue 424149 :- Fixed problem with Chrome reporting as 0 audio energy for input stream when microphone volume was low. • Issue 420866 :- Fixed Black video problem for Chrome on Android on some Samsung devices. • Issue 374104 :- Fixed A/V sync issue when FEC was enabled. 12/21/2014 5 Dealing with Audio & Video is HARD!
- 6. WebRTC Comes To The Rescue Probably the best media engine in the world 12/21/2014 6 License & royalties Quality On-going investment
- 7. Integration Options 12/21/2014 7 Do it Yourself Native AppBrowser Hybrid App SDK
- 8. Native App • Hard work • Version updates • Interoperability 12/21/2014 8 Do it Yourself SDK • Commercial/Open Source • Independent/Service
- 10. Mobile Open Source & SDKs (partial) 12/21/2014 10 Otalk
- 11. Mobile WebRTC API Platforms (partial) 12/21/2014 11 By Tropo
- 12. 12/21/2014 12 Many Collaboration Services
- 13. Hello Santa Uses an API Platform
- 14. Conclusion • Native applications vs. browser • Different options…case by case • Mobile challenge not solved yet 12/21/2014 14
- 15. Thank You 12/21/2014 15 Amir Zmora @AmirZmora
Hinweis der Redaktion
- Time - https://www.flickr.com/photos/jbid-post/6897782843/ (János Balázs) Jitter - https://www.flickr.com/photos/vshioshvili/8313738660/ (Vladimer Shioshvili) Packet Loss - https://www.flickr.com/photos/jkohen/527735042 (Javier Kohen)
- The device adds significant delay Complexity working in different layers of APIs (android)
- Do it yourself: http://www.projectcentre.com.au/Projects/tabid/213/Default.aspx Coding - https://www.flickr.com/photos/riebart/4466482623/ Michael Himbeault Gear: https://www.flickr.com/photos/17258892@N05/2588347668/ ralphbijker
- Gear: https://www.flickr.com/photos/17258892@N05/2588347668/ ralphbijker
- https://github.com/otalk http://otalk.org/ &yet http://www.openwebrtc.io/
- VoxImplant – Native iOS and Android Forge by Acision (Crocodile RCS) – fuseMe is their mobile App that allows color and some feature customization. They also provide an SDK
- Desktop iOS – Self developed on top of WebRTC Android – Using the browser due to priorities, have many requests to shift to a native app. Will do that but didn’t decide yet what approach to take https://mail.google.com/mail/u/0/?zx=62hb0jnoevwx#search/art%40gruveo.com/14956f807e9ab8a7 https://www.gruveo.com/
- Hello Santa by JibJab TokBox iOS - SWIFT & OpenTok SDK Why: SWIFT because it's the latest and greatest. And OpenTok, because they make firewall transversal and archiving/recording easy as pie. No Android