Rationale
It is possible that a certain snap is both useful in strict and classic confinement, for example for Git frontends applications only a small percentage of the feature is currently not strict-confinable (e.g. hooks), and plaintext editors that have the potential to edit system files that are owned by root/other users.
It would be great if snapcraft allows both recipes to co-exist while possibly using a different snap name (like nano and nano-classic) and let the users choose which version to install depending on their requirements.
Comments and suggestions are always welcomed.
Implementation Details
We could exploit the ability of including multiple documents in a single YAML file for building recipes for strict and classic confinement.