Sometimes applications require classic mode because either it depends on (legacy-)application that are too old, or required interfaces aren’t permissive enough yet, please consider allowing classic and strict mode snaps to share certain interfaces.
At this moment, there’s a very strict seperation, and classic snap cannot use plugs and slots to interface with an strict app, affecting even harmless and trivial things like content plugs/slots, dbus or be automatically downloaded. In my case, this is hindering me to package only a tiny component that requires classic mode, but instead forces a situation the entire application would need to made available as a snap.
Of course, I too prefer strict mode but i cannot avoid use of classic mode altogether due to legacy software. I have done my best to Isolate it into standalone daemon, but I’d still a way to make it part/integrated in application as a whole.
So per my suggestion please, please consider if it’d would be possible to have some kind of options for using content-plugs, dbus-plugs, and default-providers for a classic mode. My idea is that I would like to be able to release my main application in strict mode, and then have tiny complementary snap that would require classic mode.