Comment 7 for bug 1701232

> I question the value of extending the API to search in architectures
> other than the one we were given - perhaps snap should say "no snap
> found for 'blah' on architecture 'whatever'" to clarify the search
> parameters that were used, and point to the possibility it exists in
> other architectures but I wouldn't go further than that.

The current behaviour of snap find means that, currently on the Ubuntu Desktop for Raspberry Pi, your average user looking for snaps encounters the following:

"I want to code something"

$ snap find pycharm
No matching snaps for "pycharm"
$ snap find intellij
Name Version Publisher Notes Summary
gradle 7.2 snapcrafters classic An open-source build automation tool
$ snap find code
... a page+ of output, none of which is VS Code ...

I appreciate that telling the user a snap exists, but not for their architecture, really doesn't help that user in any immediate sense. However, making the user wade through a page of results, none of which is relevant, actively wastes the user's time compared to just telling them "yes, the snap you're looking for exists ... but the developer hasn't built it for your machine".

Just to give a little clarification of the origin of this request, it's related to https://github.com/canonical-web-and-design/snapcraft.io/issues/3969. And yes, I'm (probably naïvely) hoping that a few hundred pitch-fork wielding users might motivate the odd upstream to build for more than just the PC :)