com.spotify.Client VS autotiling

There is nothing "unsafe" about flatpak. In fact for every package on flathub you can see exactly what the "unofficial" packagers do in the corresponding github repository. For example here is the repository for Spotify, if you look at the json manifest file you can see they are repackaging the "official" Snap with the necessary libraries and scripts to support it running as a flatpak. Everything there is open source and able to be examined.

If you click on the "Manifest" link for the package on flathub, it will take you to where the code that packages the app resides. There you can review exactly what the packager does in the json manifest. Here's the one for the Spotify client, for example, which shows where it pulls in dependencies and where it downloads the proprietary code from (in this case they base it on the snap) and what commands it executes while packaging the flatpak.

Try installing it via Flatpak

Flatpaks builds are made to be reproducible. Everything is done openly and you can check how the apps like for example Spotify where made.

Why not just use the flatpak?

Judging by the manifest, the Spotify Flatpak is built from the Spotify Snap.

Check out https://github.com/nwg-piotr/autotiling I think I even left the configuration as is and the tiling is much better now.

autotiling --limit 2 is close enough https://github.com/nwg-piotr/autotiling

If you do want some "smart" behaviour as to how a new window will split automatically, try the autotiling script.

https://github.com/nwg-piotr/autotiling does it work for you?

Autotiling for i3 and Sway

Original depth limit feature contributed to the Autotiling repository by @Syphdias.

If you want to stay on sway you can try autotiling.

Have tried lots of window managers including awesome, but there's always something annoying that sends me back to i3. I use this to solve the problems you're referring to: https://github.com/nwg-piotr/autotiling