because they don't have some little additions that make a bigger impact on my workflow than I'd expect. like being able to add an empty home screen to make my KLWP setup work properly. or using folders in the app drawer. or swiping sideways on the home screen to launch an app. and so on.
Kinda like it, and mostly because it's FOSS, but will keep using "Home Launcher" (app.homelauncher, 28.0.28):
Allows to tie gestures to certain actions, though it still can't bind double tap on an empty area of the screen to turn it off. I wish either one had this option
Won't distort the icons in any way besides their sizing, as Ion Launcher does
No need to thank me, I'd like to contribute by coding but I have no idea about Java/Kotlin/Dart/etc so... I hope you keep with it though - I'd try it again in the future to see how it's going and hopefully move to Ion. Again, the fact it its FOSS it's a big plus.
Never heard of ActionLauncher until last year, but because I bought a new phone, decided to see what's out there. Multiple slidable docks that enable each app to be an app shortcut as well as a cover/folder for other apps on double tap, completely delighted me. 😉
No folders, no ability to freely arrange things, so your app drawer is everything, and unorganized. Same with the home screen.
Which, I guess that might actually work for an eink device now that I think about it (just bought a poke 5 myself), particularly one that's only going to be used as an ereader rather than a general purpose tablet with an eink screen.
There's just a minimum degree of organization that becomes a problem when it isn't there, and the device needs to be easy to use. But, yeah, I think you may have just countered my "useless" opinion. It might well be perfect for that use case, both in its bare minimum features, and how lightweight it is.