probonopd

> No, instead the user has to know where to put the .app file. Have you actually used a Mac? You can put an .app file _anywhere_, and just double-click...

Some thoughts: * Regarding the @SolarLiner screenshots in the first post: Moving and integrating are different. Even if you don't move you may want to have integration. Hence the question...

@SolarLiner > we could run into the issue that the user (or an automated tool such as a system cleaner) deletes the content of Downloads and leaves dangling desktop files...

I think we can agree that a combination of `/Applications`, `$HOME/Applications`, and `/Applications` should cover most use cases ;-)

And the rest of my proposal?

What are "content-aware filenames"?

We are not suggesting that people stick stuff like "db228740f982bb2cace6b70a4dd494ca" into filenames, are we?

Still hope that this is just a joke... 

Stuff like "db228740f982bb2cace6b70a4dd494ca" has no business in filenames since filenames are user-visible and such strings are confusing users. Let's put this string in some place where computers, but not humans,...

That is entirely not the kind of user experience I am aiming for. Check how the Mac does things, _please_.