Comparison
A Diawi alternative that remembers what you sent
Diawi is excellent at one thing: upload a build, get a link. Hashdrop keeps the link pointing at your current build, and tells you who installed it.
Diawi does one job well — drop in an .ipa or .apk, get a link, send it. If that is all you need, it is hard to beat and you should keep using it.
What it does not do is remember. Every upload is a new link, so the link you sent last week points at last week's build, and the version your tester is running is whichever message they scrolled back to.
The difference in one line
A Diawi link points at a file. A Hashdrop link points at a channel — so the link you sent a month ago hands out today's build, and you can see that it did.
How it compares
| Diawi | Hashdrop | |
|---|---|---|
| Upload and get a link | Yes | Yes |
| Link tracks the newest build | No — one link per upload | Yes, per channel |
| Install analytics | Limited | Per build and device, deduplicated |
| Accounts and roles | No | Owner, admin, developer, client, tester |
| Client sign-off | No | Approve or send back with a note |
| In-app feedback | No | Yes, with build and device attached |
| JavaScript updates | No | Yes, CodePush-compatible |
| Your branding and domain | No | Yes |
| Build retention | Limited window | 90 days, newest per channel kept always |
Where Diawi is better
It is faster to start with: no account, no organisation, no concepts. For a one-off build sent to one person this afternoon, that simplicity is the feature, and setting up a workspace would be overhead you do not need.
When it is worth moving
- You send builds to the same people repeatedly and want one link that stays current
- A client is involved and should be approving builds, not chasing them
- You need to know what was actually installed before you ship
- You want the portal to carry your name rather than someone else's