F droid is totally usable. Simply download and install the APK from their website and allow installation from unknown sources when prompted.

Unfortunately, e/OS or other Android roms are off the table as the bootloaders are locked (at least in my country they are, someone can correct me if that’s not the case worldwide).

In my experience of maintaining Arch, it’s as simple as:

-Keep your packages up to date -Keep your mirrorlist up to date -install a package called “pacdiff” and run it after every update (certain config files need to be manually replaced/updated after system updates, pacdiff handles this for you. This actually includes your mirrorlist).

Anything else really just boils down to individual issues with packages which could happen on any distro, or really and OS in general. As another user said, if you got Arch installed as a newer Linux user, you’re already doing well.

Been running the same Arch installation for a bit over a year. Minor issues here and there, but nothing out of the ordinary for general computer use.

Learning was hard. I’d say it took me a good year before I was really genuinely comfortable with Linux overall, and even then, it was quite a while longer before I felt I could call myself experienced or proficient.

I will say this, switching to AMD was a massive step up in terms of reliability. Also, and this is just my experience, but as someone who also started on Ubuntu, I’ve had far fewer weird obscure issues on Arch than on that, or any other distro I’ve tried. It’s daunting, but it’s so well documented that it’s almost impossible to have an issue with no known fix.