File locations are nonstandard.

[John-Nagle]

Ergonomic issues, or where everything goes.

• cargo appimage puts the output file is stored into the root directory of the project. This violates the Cargo rule that all artifacts created by cargo building go somewhere under "target". This interferes with source control and "cargo clean". Suggest the output file go in release/appimage/PROGRAMNAME.
• The executable is in /usr/bin in the constructed file system, and is actually called bin So, when you run the program, it's called bin in window titles, rather than PROGRAMNAME. That's a bit strange. Please use the name from the Cargo project. Serious problem.
• Asset files are in the root of the new file system. So, from the executable, they're at "../../ASSETFILENAME". This is not documented.
• cargo appimage assumes "appimagetool" is installed under the name appimagetool. But appimagetool actually downloads as appimagetool-PLATFORMSUFFIX.AppImage, so it won't run without renaming. Probably, "cargo appimage" should take care of that dependency itself, especially since appimage is not a standard Debian/Ubuntu repository item.
• cargo appimage must run in the root directory of the project to be packaged. That's not the way Cargo usually does things.

Thanks.

[StratusFearMe21]

I was able to address all of your requests accept for number 3, not entirely sure what to do about that one. At the moment I just use the AUR package name for the appimagetool executable

[StratusFearMe21]

I've just pushed an update to crates.io