“We’ll just do these steps and poof it will be on your machine! One second… Hang on… let’s try again…”
Interestingly, it seems to present shared KBs and mice as physically connected devices. Any time I use Universal Control on a Mac I haven’t before the little keyboard identification assistant that opens when you directly plug in a keyboard pops up.
I sometimes need to work on mobile development, so on advice from a sibling comment I installed KDE Connect, and it's actually pretty great and does copy/paste and remote mouse/keyboard pretty well, but you do have to a) enter the app, b) select the device, c) then finally choose the thing you want to do. They've made it about as frictionless as possible, but it won't be the same as first-class OS-level support. e.g., I can just copy some text on my Mac, and paste it a second later on my iPhone, without any manual orchestration
[0] https://blog.pushbullet.com/2014/08/20/introducing-universal... [1] https://kdeconnect.kde.org/download.html
And operating systems could allow user to select their preferred server, although I wouldn't expect Apple to allow something advanced and anti-vendor-locking like that.
I wish everything were as simple to use.
Documents is the other app I use for sending files to and from iOS (primarily iPad, from Linux laptops). But I’ve run into a lot more bugs with that, and the transfer setup process requires generating and entering codes. It’s a pretty good UX, but it always reminds you how effortless airdrop is.
I love the idea of a cross platform, open source, airdrop. It’s a lofty, but worthwhile goal.
But Apple only.. makes it much less useful, even for “Apple people”.
Do you have any sources for that? As far as I know, it's just time-sharing the same baseband and hardware used for regular infrastructure-mode Wi-Fi.
No, I should have picked my words more carefully. All I know is that they can be part of two networks at the same time.
Many Windows and Android devices have been able to share a Wi-Fi network with other devices over another SSID, for example.
The only thing that's complicated is if a device needs to be a 802.11 station on one frequency/channel, and a host or P2P device on another, but that's almost always avoidable.
Everything else can be done purely in firmware or software.
I use apple's IP audio streaming protocol (forget what it's called, air-something) to play music over a couple of edifier-brand speakers from a Linux desktop which is running pipewire's FOSS implementation of the protocol. I don't even buy apple products but i ended up using it because there's no way to just netcat samples onto these things.
Airdrop Discovery is slow. Notification of an incoming file is slow. File transfer startup is slow. File transfer completion is slow.
You have to wait at every step and you cannot stop watching it, lest the transfer fail.
The UI for iOS isn't very good either. It floats on top of everything. It's easy to dismiss and impossible to bring back without starting over.
It's a great idea with bad UX, but still better than nothing at all.
The lack of notification when you are receiving is annoying though.