Help shape what's next.
If there's something you want to see — a feature, a fix, a change — tell us.
How we decide what to build
Repeat requests win
An issue that several people arrive at independently, each describing the same dead end, moves ahead of a feature only one person has asked for. It isn't a strict vote count — a single well-argued case for something that unblocks a whole workflow carries real weight — but recurrence is the strongest signal we get.
Nothing ships that weakens the privacy model
Some features are genuinely useful and still don't make the list, because delivering them would mean storing your files on a server or holding a key we could be compelled to hand over. Server-side search across your transfer history is the classic example. Where there's a design that gets most of the benefit without that trade, we'd rather spend longer and find it.
It happens in public
Development, issues and discussion all live on GitHub. You can read the code that's running, watch a fix land, and disagree with a decision in the open. Small fixes ship continuously; larger features land in numbered releases so you can see what changed before you update.
What's useful to tell us
Reports that include these get acted on much faster than a one-line request:
- Which platform and OS version you're on, and which AlterSend version.
- What you were actually trying to move — file types, roughly how large, one file or a folder tree.
- For a bug: the steps that reproduce it, and whether it happens every time or occasionally.
- What you use today instead, and the specific moment it lets you down.
- Whether the network involved was the same Wi-Fi, two different networks, or something restrictive like a corporate VPN.
- Offers to translate the app or the site into another language — these are always welcome.