Glad to hear. In the context of WebRTC PaaS, how is MeetingKing related if I may ask?

Thanks!

John, thanks for taking the time to explain where you’re headed.

For a scheduling system, this seems like the right approach – you’d prefer being agnostic and support whatever your customers are comfortable with.

We’ve built deep integrations (Turbobridge for SIP / telecom — webrtc coming!), Twilio (webrtc with flash fallback) for core audio options, and Glance for integrated screen sharing. At some level even a meeting management platform like ours needs a core set of capabilities and a business-level arrangement with our partners.

But — we have increasingly found pressure for a variety of other options already in use out there. For us to build and maintain deeply embedded integrations for all these options would kill us 🙂 I think there’s a lot of interest in bringing personal, consumer-oriented tech into the business setting. That leads us to look for easy wins, such as our appear.in integration.

We will, for example, launch a group Skype call if that’s what you already use and prefer. Same for a Google Hangout (soon) or appear.in, which is drop-dead simple for people to join and use. And there are probably more of these “arms-length integrations” as well.

Because our value focus is on meeting management, we want to be as accommodating as possible for people’s preferred communication technology. The easy integration wins are great for that.

Art, thanks for the comment. Gruveo has been a surprise to me in many ways in this regard.

– Basic integration is free
– All the necessary functionality is oftentimes already there
– The ever increasing brand recognition for Gruveo means a familiar widget and less of a barrier for users to click that “Video call” button
– Since Gruveo is running a public service, it’s in our best interest to keep the solution secure and working – something a vendor gets to enjoy at no cost.