Comment 1 for bug 1603481

I definitely understand the desire, but it's a slightly hard one to solve.

The problem is not technical though, but organizational. Everybody wants every command to be top-level, so offering this would mean moving what is today a flat snap namespace into being a flat application namespace, which would be somewhat unfortunate for the ecosystem.

Perhaps we can do something else to fix the problem, though. We should be able to easily offer a mechanism to put every application name from a specific selected snap in the current $PATH, which means all interactions with those commands would resolve into that snap.

This would have to be a user choice, but might solve the issue you're concerned about.