As some users already stated there are yet several drawbacks in using Snaps (themes, extensions, init time, …). For instance, installing it on a system that doesn’t have snap pre-installed the icon will not appear in the menus right after installation is finished because snap path is not loaded yet. Trying to install a legacy version of the package is also not an easy task, because the packages names are the same, including dependencies. Apt/Debs installations may conflict with Snap installations, because now one is a dependency of another. It even takes out the opportunity of other distros build their own packages, because packages name are already taken.
Also, breaking a system doesn’t necessarily means breaking it completely, but if the user is used to do something and having a result, if he/she does the same in an updated system it is expected the same result. So, if chromium is installed using apt/deb is expected to work in a way but this is not true if instead a Snap is installed. Themes are the the easiest example to give, as you may see in the picture. I’ve test with several themes, including Arc and Numix that were installed via apt. Arc was the only one that worked, but even Adwaita didn’t work as expected.
Please rethink this idea of converting actual apt packages into snap wrappers. I know it makes sense for Canonical as a market move, but it’s totally against system’s transparecy, user freedom and project coherency, things that Canonical are known for. You should use Snap but please don’t mess up with apt repositories, just remove the packages and instruct people to use snaps or the store. Inexperienced users will probably use the Store anyway and advanced users will notice that the only available source is snap.
