It can run from any path so long as your plugin host or DAW is happy to load it from there (the plugin APIs define standard folders plugins should be installed to, but lots of host allow other paths).

Once running it will try to create some directories in known locations on your OS for storing libraries, presets, preferences, etc. https://floe.audio/docs/reference/file-locations

Not quite as generic as that. I suppose there's 2 types of users at the moment.

Musicians who just want load up virtual instruments (whether that's 'real' instrument, or synthesised-based), play them, but then also use Floe's GUI to morph the sound into something different using layers, granular, FX, etc.

Or alternatively, sample library developers who want to create a curated sample library package for musicians. They configure the sample library using Lua (and set a background image and icon) and create a bank of presets - and then musicians can load that packagr into their Floe instance.

Since early 2026 it's mixed AI and handwritten. Before that it was mostly written by hand. Quite a lot of the code goes back to 2018 even. Typically, I do back and forth with Claude Code agents on new features and bug fixes, reading and editing code along with it.