[luckyshot]

Great project! Thank you for building it.

If the UI was simpler and more "Apple-like" (hate to say this) I could convince my non-tech coworkers/family/friends to use it.

Also, could you auto detect the other peer's OS? You could skip an extra step and UI element. Do you need it to know which WiFi bandwidth to use?

[spieglt]

Thank you! Yeah, obviously the UI is a weak part. I'd like to improve it eventually but as a one-person project I don't want it to have as minimal of an interface as AirDrop. With all the ways transfers can go wrong, I want that information to be in the user's face so they can submit issues and I can help debug easily.

And no, it can't detect anything about the other device until they're on a WiFi network together, and that can't happen until it knows the peer's OS because it has to know whether it or the peer should be hosting the hotspot. Windows has precedence, then Linux, then Android. (The iOS version doesn't need to know the peer's OS because iOS and macOS can't stand up a hotspot programmatically anymore, so it always has to join.)

[luckyshot]

Thank you for the detailed explanation, it's not my specialty yet really fun to scratch a bit of the surface in other aspects :)

[nullderef]

So how would a transfer between two iOS devices work? Neither would be able to create the hotspot, right?

[spieglt]

Correct, Flying Carpet doesn't work for Apple-to-Apple transfers, but AirDrop already fills this need.