I set out to build Etcher for the Pi4. I didn't succeed, but @futurejones did. If I had succeeded, I would written down the recipe (and test-baked it a few times to make sure I hadn't forgotten anything), and then I would have posted that recipe here for others to follow. I personally hadn't intended hosting or posting a pre-built package, even if I HAD succeeded, because I don't think people ought to download software from random individuals on the internet, even ones as unfailingly honest as myself
or as clearly clever as @futurejones. He's gone way further than I would have, with his own github site, and many clever scripts, and his own project as a kind of wrapper for the balenaEtcher project. I'm very glad he took up the challenge, and I thank him for all his work.
@futurejones provides both the scripts and a pre-built package you can install. I recommend that you follow his instructions like I did, and build it yourself, but anyone is free to choose differently.
I have NOT downloaded
his pre-built package, I have NOT tested
his pre-built package, I have NOT used
his pre-built package at all, and I don't intend to. And, I hope @futurejones understands that there's nothing personal about that.
All I'm attesting is that, at the time I did it, both my very slightly modified version of his scripts and his exact scripts, which I looked through, succeeded in building and packaging a recent release of the balenaEtcher code, and that those packages, when installed on my Pi4, resulted in a working app.
NOTE: the balenaEtcher developers are aware of @futurejones 's work, and the very best outcome would be for them to follow his lead, or learn from what he did, and make a Pi build part of their standard build processes, and then offer it on their website. In which case, I would download it, since I feel that somehow they've got enough online presence and size and status for me to trust them. (Again, no offense intended towards @futurejones.) This process really belongs upstream with those whose code it is.