Skype this week launched a new screen sharing feature on iOS and Android devices, allowing users to share their smartphone screens with any of their Skype friends. Microsoft said that this should be useful for helping family members figure out their new smartphone, shopping online with a friend, and more.
Skype on desktop already supports screen sharing, but this is a brand new addition for the iOS and Android apps and was previously in beta testing earlier this year. To find the feature on your iPhone, start a Skype call, tap the "..." menu at the bottom right of the screen, and choose to start sharing your screen.
The company has also redesigned the app to streamline video calls: users can simply tap to dismiss all call controls so they can see their friend or family member without any obstructions. To remove all UI from the call, they can double tap the screen, and then single tap again to bring everything back.
Skype for iPhone is available to download for free [Direct Link], and the new screen sharing feature is available on devices running iOS 12 and up.
Top Rated Comments
(View all)I’ve spent many times hitting my face against a brick wall trying to explain to my mum what to do on her phone to fix/do general things and this should make that much easier.
Is there something similar for the Mac OS?
It's actually built into the iChat protocol that still lingers in Messages for Mac OS.If you are communicating with someone who uses iMessage you can share, and even control each others screens if they both are using Mac OS.
On Mac OS, the feature has been around for over ten years now I think.
And what if you don't have friends, only colleagues? Is it restricted to friends? XD
Skype is the consumer product; Teams (née Skype for Business, Lync, OCS and all sorts of other crazy rebrandings) is the new business version.And if so, how do they know you're friends?
[doublepost=1559766701][/doublepost]
The user was supposed to have to opt in on Group FaceTime as well by answering the call, but as we learned the potential for privacy-leaking bugs for such a potentially-invasive feature is pretty high. That is what I meant by "what could possibly go wrong?"
I don't think "we risk privacy bugs; ergo, we shouldn't offer this feature at all" is a reasonable path here.