WebRTC is an out-and-out browser based technology. When we talk about WebRTC, perhaps the most imaginative might picture some technology on a mobile or at best a native application instead of a browser-based one, however most would imagine nothing but browsers and some story around it. Now WebRTC has gone stronger and its implementations have crossed many boundaries. WebRTC on mobile apps is no longer a fantasy. Here at Algoworks we have successfully created functioning mobile apps using it and they are performing better than predicted. This slide presents you some of the best Tools & Tips for Native WebRTC Mobile App Development. Don't miss this out. ;)

1. Native WebRTC Mobile App Development
Tools and Tips

2. WebRTC on mobile apps is no longer
a
fantasy

3. WebRTC is awesome and it is considered as future of internet based communication.
It has gone stronger and have crossed boundaries.

4. Challenges
in using
WebRTC for Mobile!
Challenges

5. BROWSER BASED CHALLENGES
Challenges

6. Even if we focus on developing a browser based WebRTC app, not all mobile browsers
supported WebRTC features like PeerConnection or MediaStream API.
Since not all devices support all web
browsers, and not all web browser
support WebRTC, clashes are
bound to occur.
Challenges

7. DEVICE BASED CHALLENGES
Challenges

8. Different devices, even in the same
Operating system family, have
different implementation for the
microphone, speaker, and
Bluetooth builds. These require some
special handling from developer point
of view.
AUDIO HARDWARE
Challenges

9. WebRTC is a processor intensive API. Also most WebRTC internal APIs are supposed to
be supported by at least ARMv7 CPU architecture with its NEON extension.
Though Audio can be processed in CPU with NEON, video cannot. Since the old Android
devices, iPhone 3G and other previous devices do not have ARMv7 CPU architecture,
WebRTC’s reach becomes limited.
PROCESSOR LIMITATIONS
Challenges

10. Once again since iPhone is a CPU-
intensive application, it drains a lot
of battery.
Advancement in technology will
also eventually remove these
limitations, for example Audio
Acceleration feature remarkably
cuts on a lot of CPU processing and
thus saves a lot of battery.
BATTERY PROBLEMS
Challenges

11. Tools to implement WebRTC
on Mobile
Tools

12. The biggest
… is the fact that Apple does not support WebRTC on its own. You would need
to create your own custom SDK for iOS support or you can use third party
SDKs and significantly reduce your app development time.
Tools

13. Tokbox and its API platform
OpenTok are currently among
the most used WebRTC SDKs
The platform is robust, full of features,
and most importantly comes with
plug-ins to make it compatible with
internet explorer(the bane of web
developers).
Tokbox is used by major brands like
Bridgestone Golf, Major League
Baseball’s website MLB.com, and
Universal Music Group.
Tools

14. Tools

15. HookFlash offers a service
level agreement (SLA) for
premium accounts.
Only WebRTC SDK that
first provided support for
iOS app development,
which was followed by
Android and JavaScript
support.
It offers commercial pricing at one tenth of one cent per API call for high quality messaging, voice and video chat for
developers and enterprise customers.
Tools

16. Android SDK is currently in
The company already has its mobile app available
for both iOS and Android, so an iOS SDK should
definitely be more than a vaporware promise.
Tools

17. Open Clove offers two options for WebRTC
support, with a large number of demos and
sample code with the pay option.
FreeMAD offers free source code
for two-way communication.
Peer-to-peer communications,
with video the default voice and
messaging options are available
by adjusting flags in the
template.
Tools

18. The company provides WebRTC SDKs for both
Lists Airbnb, the Democratic National Committee, eBay, Intuit, and Hulu among its
users
Make every device a phone, is Twilio’s
Tools

19. WebRTC is one of the most worked upon technology.
It is still a growing field and we are going to see a lot of improvement in it in coming days.
However the technology is viable even in the present scenario.
So if you are thinking about using WebRTC for your communication solution, you are going in the right
direction! :)

20. sales@algoworks.com Toll Free : +1-877-284-1028
Author
Director
Rachit is leading the mobility business
development function, mobility strategy and
consulting practice at Algoworks. He is an
expert of all mobile technologies and has
experience in managing teams involved in the
development of custom iPhone/iPad/Android
apps.
Rachit Agarwal
Write to me at
rachit.agarwal@algoworks.com

21. Mail us at:
sales@algoworks.com
Official Blog Link:
http://www.algoworks.com/blog/webrtc-mobile-app-development/