They found code for kind of that in the new Google Play Services bundles ( https://www.androidpolice.com/2019/06/30/google-fast-sharing... ). They theorize in the article that it uses the same technologies as Airdrop, so they might be compatible - though I doubt it.
I use https://dro.pm a lot to share files or links. Since the links are super short (I just made https://dro.pm/a --- note that it'll expire in 12 hours), you can just give the link to someone over the phone, put them in a presentation, or just share files independent of any operating system.
I even use it even between my laptop and my phone fairly frequently, since the top suggestion on my phone keyboard in the browser is dro.pm and I just have to add a slash (long-press "m") and a letter. It's quicker to use dropm than to open a chat with myself or send myself an email or something.
Of course this is just protected by https, and although it is source-available and the links are really gone after expiry (or when you edited it, the old contents are irretrievable), magic-wormhole is superior in that you don't have a trusted third party. For the cases where the other party doesn't have magic-wormhole installed, this might be helpful. This also alleviates the requirement of WebRTC for both parties to be online simultaneously.
If I understand it correctly, the rendezvous server is not a trusted third party, just a message relay. They wouldn't be able to read or modify your file transfer's contents.
Knowing Apple, such an effort would likely be destroyed by an army of lawyers the moment you bring out an app that provides such features.
The Apple ecosystem is very closed and Apple will fight tooth and nail to keep it that way. Removing vendor lock-in would, after all, allow users to try switching to another brand without an enormous amount of hassle.
Apple's open-source mDNS/DNS-SD implementation mDNSResponder underlies Android's NSD API, so I could one day see seamless interoperability over Wi-Fi Aware being a thing. I wouldn't bet on it happening, but given Windows (which ships with an mDNS/DNS-SD stack) and Android will be doing it before too long, I wouldn't be surprised to see Apple join the party.
I hope we'll one day see proper support for mdns in Android. Devs shouldn't have to go out of their way to use the special NSD API to provide mdns functionally in their apps. It should just work at the system level, which to be clear, it does not. It's been years and years in this state, so I can't be as positive.
Incidentally, Wi-Fi Aware is based heavily on AWDL but the Wi-Fi Alliance made a number of breaking protocol changes in the Wi-Fi Aware standard. This isn’t exactly Apple’s fault - it could have been interoperable.
> The Apple ecosystem is very closed and Apple will fight tooth and nail to keep it that way.
In general you are right, Apple is very adamant about keeping full control over their ecosystem (and locking users in). They even sponsor a C compiler project so that they can avoid gcc. There are exceptions though, like AirPrint which is a marketing name for open standard technologies: https://wiki.debian.org/AirPrint
The switch to llvm/clang was about more than just avoiding gcc… it was also about filling holes in gcc’s functionality. Swift for example is heavily rooted in llvm/clang because at least at the time, llvm/clang was capable of a lot of things that gcc simply wasn’t, and the arcane nature of gcc’s innards made it unnecessarily difficult to add missing features to. Of course, GPLv3 poses issues too, but that’s only a single factor among several in Apple’s decision to deeply invest into llvm/clang.
Apple wouldn't allow a solution that's integrated within the OS, but if you want to share data between devices, AirDroid [1] is one such free service. It is available on multiple platforms, including Android, iOS, macOS, Windows and web. Use web.airdroid.com on devices/computers where you don't want to install the application.
Exactly. They are well aware of the fact that Android users are left out in the cold. They are only able to do this because of their market position. If they really cared all they would have to do is create an iMessage API and the community would build it for them, but they would rather try and drive iPhone sales by building a walled garden.
I mean, wink wink, it's exactly what they wanted to do. Apple wanted a closed garden, they built it, and they won't allow anybody in from outside, and for now it's working, so, for them, there's no problem.
Steve (Jobs) famously, and impulsively claimed they were going to release FT as open source - so impulsive that he never even checked with their lawyers first, because it never happened due to legal/licensing issues, not because they didn't want to.
Do you think that's true, sounds exactly like a publicity stunt to ensure a big launch in the face of having no answer to "is it interoperable".
If you say "yeah sure it is, we're even releasing it as open source" then you prevent the product falling at the first hurdle because people want an interoperable solution. Once you have adoption network effect carries you through.
Sounds like most probably a standard corporate lie by Jobs; do you have evidence to the contrary?
I guess you mean something that is first party on both platforms? Otherwise SMS-like communication is obviously a solved issue (Signal/WhatsApp/Messenger et al).
> Does Android have something similar to iMessage?
Kind of-ish. The RCS support is rolling out slowly. Of course there is a big difference in that RCS is not end to end encrypted. Also, there is nothing stopping Apple from implementing RCS as well, but I doubt they will do.
If Apple does adopt RCS, it's likely only as a fallback for iMessage, much like SMS today. And rather than Apple abandoning control over their messaging platform, I'd sooner bet on Apple releasing iMessage and Facetime for Android with a small subscription fee. Probably in the range of US$1-$2/month.
If there's one thing that Apple hates more than lost profits, it's handing over control of anything to carriers. Cheap-subscription iMessage/Facetime for Android would strangle RCS/Duo in the cradle and put a thumb in the eye of the carriers, while bringing in some steady and significant regular revenue. Let's not forget that Apple is already offering a subscription service on Android, Apple Music. They're not averse to the concept.