Description
Advanced users will want to run newer and newer versions of ipfs (eg release candidates, etc).
While i'm perfectly comfortable replacing the binary at /Applications/IPFS Desktop.app/Contents/Resources/app.asar.unpacked/node_modules/go-ipfs-dep/go-ipfs/ipfs with a shell script that uses the ipfs in my $PATH, it may be nicer to make it a gui config option.
Though, maybe warn users that it's an advanced feature and that things may start breaking for them (for example, if the installed version doesn't work with the api client IPFS Desktop uses, or the binary in the path is broken, etc), which may be hard to recover from.
Just a suggestion-- perhaps the best answer is "no, do your shell script replace manually, and deal with the consequences" to avoid bad things.