I think its a very valid point that patrol is not exactly plug and play, to the point I do recommend pairing with a mobile developer for a few days to get the infrastructure up and running.
A couple of questions on Moropo, I may give it a quick look.
Is it aimed at mobile apps and not just mobile web apps, apps tend to be a bit more complex with the interactions.
When an app transitions to webview or native side, that could be clicking on a notification, a google login, a 3rd party overlay payment system or even just native device configuration does it handle that as smoothly.
Does it handle parallel runs?
With 2, 3 and 4, sometimes I find the cons of avoiding those outweigh the potential benefits.
Often my first question is are the developers building the product going to be comfortable using the tool, they in my experience tend to be more comfortable when 2, 3 and 4 are in place. Even things like selenium I find developers wont touch themselves so they drift more towards tester rather than developer friendly which in turn creates both a communication and collaboration distance and inefficiencies.
That might be worth looking at in terms of promoting the tool, is it developer friendly and are they going to be happy using it. Do you have a base of developers who would recommend the tool or do you feel it is more aimed at less technical testers and see that a postive?
I think its fine for some teams to see some things as a strength whilst others see the same things as a weakness, different contexts are important and like you I have my own bias.
Lean teams can go both ways, if a distance is created from the developers and that team only has developers or they decide at some point to drop the tester out will they actually continue to use the tool?
Either way if it is app focused and not web app focused I will likely give it a look and see if I can provide a better informed view than I have now.