This is a personal passion project of mine, it is still in its early infancy (many core features are still missing) and the development is slow but deliberate.

why should I care?

if you care about speed and deep integration with the OS this project might be of interest to you.

why?

Wireless file sharing between my devices is still unnecessarily slow, half-baked, and unintuitive. Direct-Share is my attempt to build a file transfer tool that makes local file transfer more seamless than:

Android ↔ Android (Nearby Share / Quick Share)
Apple AirDrop
LocalSend
Blip

…but for Linux desktops and Android phones, using Wi-Fi Direct.

what?

Python, GTK4/Libadwaita on Linux
Kotlin, jetpack compose on Android

if you want to stay up to date with the project or want to know or read more, you can take a look at the GitHub repo

you are viewing a single comment's thread
view the rest of the comments

[–] isVeryLoud@lemmy.ca 1 point 4 months ago (1 child)

Why not build that into Localsend instead of developing a separate solution?

permalink

fedilink

source

parent

hideshow 1 child comment

[–] Im28xwa@lemdro.id [S] 1 point 4 months ago

The honest answer is because I prefer making my own thing for my own exact problem over trying to make someone's else tool do or behave in a way that it is not designed or made for, it is a bit philosophical for me but yeah, I am not willing to put all the effort into something that I see is solving a problem and making compromises and ignoring things in ways I don't agree with, not to mention the UI/UX disagreements I have, if localsend was my thing, it would have been very different from what we have right now.

And also I am doing it in spite, this thing have been bugging me for years and no one is willing to put the time and effort to do it the way I think it should be done so I am doing it myself...

permalink

fedilink

source

parent