But localsend has worked well for me. Yes, it requires an app but if we could get vendors to bundle that rather than a boatload of bloatware.
I know that it would be to optimistic to hope for Google.
Spread the word.
That's a clearcut case of absolutely willful trademark infringement, and it will not go well for the authors when (not if) Apple happens to cast their gaze in that direction.
Wait, seriously? iPhones still don't support Bluetooth file transfers? I knew this was the case with the first iPhone but I just accepted that's a limitation from the OS being still an early release of a brand new product with limited functionality, I wouldn't have expect this to be the case after 15 years.
Anyway, I'm still baffled we never got a standardized Wi-Fi file transfer protocol, like with Bluetooth but at wi-fi speeds.
Oh right, nevermind, Apple wouldn't have supported anyway versus their own proprietary one that only works on Apple devices.
(If you're talking iphone to Android, nvm)
Bluetooth can work, but it is slow as hell, and Apple doesn't support it.
Cloud services are convenient, but you not only you need some signal, but you also uses up your data plan.
If you have USB OTG support, you can simply use a thumb drive, like with your PC, but it is cumbersome and you need the hardware.
There are some somewhat proprietary systems like QuickShare and AirDrop, which are supposed are great when you have support which is not always the case.
Other options include having one phone act as a WiFi AP and host a local HTTP server, there are apps for that (ex: MiXplorer). A bit uncommon, but the advantage is that only one phone needs to do weird stuff, for the other, it is just downloading from a URL.
There are also apps like SyncThing based on P2P networks.
Generally, phones are pretty terrible at dealing with files. Their OS is designed around apps controlling their data rather than around interchangeable files like traditional desktop OSes. The way they want you to work is not by exchanging .gpx files but instead by using some built-in "share" feature of your hiking app. It may be .gpx under the hood, but they don't want the end user to see a file.