3 ms·
You're right. It did come off trollish. Wasn't my intent. I'm sorry to both parties. Both WebAPI and WebRTC will produce awesome collaboration apps. Wins all a
by BrandonSmith 15y ago
You're right. It did come off trollish. Wasn't my intent. I'm sorry to both parties.
Both WebAPI and WebRTC will produce awesome collaboration apps. Wins all around.
But how, exactly, do the two fit together? Is WebRTC a low-level implementation of protocols, codecs, and transports whereas WebAPI provide the friendly developer-oriented APIs?
Will WebAPI provide hooks for standard widgets for dialer, SMS, contacts, etc?
- MatthewPhillips 15y ago> But how, exactly, do the two fit together? Is WebRTC a low-level implementation of protocols, codecs, and transports whereas WebAPI provide the friendly developer-oriented APIs? They're not related. WebRTC is a video chat/conferencing project. > Will WebAPI provide hooks for standard widgets for dialer, SMS, contacts, etc? Yes, that's its precise purpose.
- hrabago 15y ago> > Will WebAPI provide hooks for standard widgets for dialer, SMS, contacts, etc? > Yes, that's its precise purpose. I'm not seeing any indication that standard widgets are even in their goals. For instance, their Telephony API [1] lists functions that an application implementing its own UI might call, but nothing that indicates that those are UI widgets or expose UI-like functionalities. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=674726 https://bugzilla.mozilla.org/show_bug.cgi?id=674726
- MatthewPhillips 15y agoWell, this is WebAPI after all, not WebUI... but why do you think they should implement UI widgets? That goes against the grain of the web.
- hrabago 15y agoI don't think they should. In fact I hope they don't.