fleek VS rasp-nix

I think the fastest path to adoption is to build a front-end for nix so that non-technical users can use it like they would Ubuntu. Users could select packages and edit system config through a GUI, which would be built/deployed when the the user clicks "save" or whatever, with an "advanced" mode where users could edit and add extra text config if they wished. SnowflakeOS [1] and Fleek [2] are admirably starting to work towards that, but there isn't enough of a concerted community effort to make it a first class feature of NixOS. If/when something like this were mature, you could then take it to the next level, where you could have something similar to an "app marketplace" where users could share flakes or sets of config that do things, like "Jake's blinged out desktop" or "Home router setup", essentially adding an additional layer of easy composability on top of base packages that most systems support.

Apologies if there is already a concerted community effort here and I was unaware of it.

[1] https://snowflakeos.org/

[2] https://getfleek.dev/

If I understand it right, https://getfleek.dev/ will turn a simpler yaml config into home-manager/nix/flake config. Might be a simpler way to get started.

Haven't started down into the Nix abyss myself though…

Coincidentally I came across Fleek this morning, which appears to be a simplified Nix abstraction?

https://getfleek.dev/

Assuming that rebasing under uBlue is no different than under regular Silverblue, it's good to know that experimenting as such can populate your home folder with unwanted (dot)files. Therefore, either make use of a dotfiles- and/or home-manager like Fleek or backup your home folder (perhaps with Btrfs as demonstrated by Stephen's Tech Talks).

Seems like that might be the way to go, I have also found fleek and it does exactly what I want but idk if i want to use nix.