I think you might misunderstand what GitHub actually is.

It's a version control service for source code and being able to download released artifacts is an extra feature on top of that.

git = software to manage and track changes to source code

GitHub = a service to host your git source code repositories

The uncompiled source code is kinda the whole point of GitHub in the first place

github's primary purpose is for it to host uncompiled code.

This is like you complaining that grocery stores sell eggs, flour, and butter, when all you need is a cake.

edit: the post I was replying to seems to have changed. It originally said that github should not host any "uncompiled code"

Ah, I see. I don't think that would be very well received - GitHub's primary use case is to be a place to share code with other developers, shying away from that would be a fairly fatal blow to GitHub. You'd just see projects move over to other "Forges" like GitLab or Gitea/SourceHut/Codeberg (anyone remember SourceHut?) which would have the same "problem".

As Wesley pointed out in the other reply, GitHub does have some other features bolted on top of it (such as GHCR, CI/CD, Artifacts, Gists, Pages, Issues, Wiki, etc the list goes on) but at its core it is somewhere to host a git repository.

If we were talking about commercial applications, I'd say that's a marketing / distribution issue by the company producing the application you're looking for. However, given that software on GitHub is more often than not open source by individuals (or sometimes a group of individuals) it's not really reasonable to expect for every one of them to go make a page that hides all of the code and only offers downloads. People already have a bit of a bad habit of saying that READMEs are not flashy enough, so I highly doubt a plain text page that just links to some binaries are going to be sufficient for most people.

I know that I personally wouldn't be able to spend the time (let alone the ability - I'm terrible at frontend!) to make nice pages for any project that I publish, and that's okay because I'm not selling said projects - I share them with the world in case anyone is interested but still the idea behind me publishing something on GitHub is not for visibility / popularity, but so that maybe at least one person in the world can learn from my code (whether that is good habits or bad habits 😅).

That also doesn't address another problem, which is that a lot of code on GitHub is intended to be used as a library for other projects to use. These don't really have downloads in the way of binaries - you're expected to compile the code yourself so that you can use it within your own code. Sometimes there are ways to make that downloadable, I primarily work with Java / Kotlin so I could provide a download as a jar... but usually you publish those libraries to some sort of Maven-compatible repository so that you can just declare it as a dependency in your own project. Or maybe its a C/C++ header-only library where there is literally no binary that you could publish. I suppose you could direct link a download to each header file, but you'd still just be getting... code.

TL;DR - GitHub is working exactly as it is intended to. It'd be like going to a hardware store and saying that they should offer pre-built furniture and hide all of the tools / materials in the backroom. They might have some appliances and pre-built furniture (off the top of my head things like washers, dryers, and refrigerators where you're not really likely to build your own) but that isn't the primary point of the store. For Liftoff specifically, if you're wanting a more traditional place to download the app, you'd want Google Play, IzzyOnDroid, or the Apple App Store. Just like for furniture you'd go to a furniture store - but if you want the tools to perhaps touch up / fix some furniture you've purchased you'd go to the hardware store (GitHub in this example).