There were too many simple use cases that could not be done simply, compared to mmex.
One example is credit card partial chargeback/refunds. The dev suggested to edit the initial charge and substract the refunded amount. I dont want to do that. I like to keep a 1:1 mapping of transactions.
Also income vs expense accounts, instead of payees. If Amazon refunds me partially (let's say $10 from a $100 purchase) it now creates an Amazon income account with $10. I had an Amazon expense account of $100. Both accounts are not linked in any way and it's impossible to know your Amazon balance ($90).
I buy a lot of stuff for my girlfriend and she pays me back around the end of the month. Keeping track of her balance is not possible with Firefly.
A few other things were not working properly or at all.
Dev is very nice and active but I doubt he has any accounting background. Firefly turned out to me as a prettified excel sheet, not a double entry book keeping.
It's also nifty that it exposes pretty much all of the functionality via a REST API, complete with the ability to manage OAuth clients/tokens. Not something I expected to really leverage, but have been surprised how frequently it's come in handy.
It's more akin to a self-hosted version of Mint. Combined with the Plaid connector[3], I find it the easiest to use for my workflow. And despite the instructions, you don't need a paid dev account. The free Plaid account will let you access up to 100 live financial institutions.
[1] https://github.com/firefly-iii/firefly-iii
[2] Live demo: https://demo.firefly-iii.org/
[3] https://gitlab.com/GeorgeHahn/firefly-plaid-connector