![]() I found some public signals made by the community but I missed them: I didn’t pay attention to that post from Lee Martin on Twitter who mentioned it. Regarding on the public announcement, I searched on the official Apple release notes but the one from iOS 14.3 was really light on that point: Nothing was announced. In fact, they were 2 main reasons for that: Firstly, there was no real public announcement about that compatibility made by Apple and relayed by the community and secondly, the way I blocked my application from being used from no compliant browsers on iOS was a ‘blocked-for-ever’ strategy. That’s why, I tried to summarize what I learned from that story to that post. I was waiting and although I was following all the WebRTC news on the Internet, I missed the announcement… It was working from several months and I were not aware of that compatibility! Not really for my personal usage but because it easier to let end-users connect to my Web application with the browser they like and not have to force them to use a browser they don’t really use. Having the possibility to use my favorite browser on my iPad to connect to my WebRTC application was really something I expected a lot. Slug: “webrtc-chrome-ios-compatibility Introduction It’s a great improvement that will help us to build Web application on mobile devices.” Starting iOS 14.3, it’s now possible to use Chrome or an alternative WebRTC compliant browser to Safari to have audio and video calls with an iPad or an iPhone.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |