Let’s try a metaphor. Say I have a bike. Someone’s trying to sell me another bike, based on it having two wheels, both compatible with standard tubes, and optionally having a luggage rack, if I bring my own and attach it. Then I would also be asking them what their bike actually does and why I should bother swapping mine out for theirs, because it just looks like an extremely standard bike. It doesn’t mean I do not know what a bike is.

The question about lawnchair specifically has mostly been answered by comments now, but the website still does a very poor job explaining what it does over any other launcher, especially compared to the stock one.

Sure, but what are those? Maybe I’m the issue, but the website seems to be made for people who are already intimately familiar with the possibilities of a custom launcher, because they’re hardly listed anywhere, there’s no list of features or anything.

Well, there is one list, but it’s

1. “Pixel design, but more customizable somehow” How? Dunno, isn’t explained
2. “The latest android features” which is cool but also something I have on my stock launcher
3. “QuickSwitch support” which is not explained (some research makes me believe it’s API access to the default launcher that’s needed to show recent applications, which is also a feature my native launcher has) and needs root according to the FAQ. So can I not access my recent applications if my phone isn’t rooted?

And the wiki is just from the dev side, which is interesting, but doesn’t provide the proper info. I’m sure it’s cool if so many people here like it, but the website’s doing a poor job at showing that off.

Edit: Basically it seems to me like the selling points of most Android forks, which are generally “We’re slightly worse in some areas, but generally have feature-parity, possibly slightly better customization/settings, and you’re free of Google spyware” which is admittedly a selling point, but here you don’t even get rid of spyware if you’re on regular Android, and if you are already on a fork, then why bother?

I just checked out the website and I’m having a hard time understanding what the point of it is. I’ve never installed any sort of custom launcher, so maybe I’m missing out, but the application advertises itself on being very similar to the regular pixel launcher, not needing root access, and nothing else. Even in the FAQ I only see that it supports some plugin that upgrades some widget, unless you have root where it supports whatever you can do with the “recents api”. Neither of those seem remotely worth it. So what does it actually do?

On your point about it being “easy” to install containers via the app interface, are there any guidelines for how to configure them when all you’ve got for reference is a Docker Compose file?

A lot of stuff matches 1:1, but there are often oddities here and there, and I’m still not entirely sure of the correct way to configure storage. Some guides say to create datasets in the pool and then configure some to use the “apps” preset, while others should use “generic.” Others say to just use the automatic permissions checkbox, and others still tell you to check the “Use ACL” box. When I haven’t found a guide, I just created the datasets manually, set them to “apps,” and so far it has worked.

And when I want to use Docker containers normally, I’ve been advised against it. There used to be something called “jails,” but that was deprecated with the new Containers tab in the GUI. Apparently, that’s being dropped again for some reason, but the jails are still deprecated, and any time I search for how to use Docker Compose, I get so much conflicting info. Some say to just run docker compose as you would on a regular server via the command line, while others say that could break the system and tell me to just use VMs instead, and it’s all a mess.

The SMART stuff I mentioned was definitely my lesser worry, just a mild annoyance that tipped me over to consider switching, but the apps feel like I’m learning a whole new abstraction layer instead of just writing a Docker Compose file with input fields. Maybe that’s just a me problem though and I’m simply refusing to adapt, I am really not sure.

Huh, sound pretty simple overall. I was mostly afraid I was missing some key features that would be painful to set up and were needed for a NAS, but apart from the filesystem and SMART tools, this isn’t much less setup than I had to do with TrueNAS. Thanks!