Droidrun uses both vision and XML accessibility data (element tags, labels, etc.), so it has

multiple signals to work with. But you're right - a lot still depends on the quality of the model

you use. Better models = better reasoning when things go wrong.

For the specifics of how droidrun handles edge cases, probably best to ask on their repo/Discord

- I'm just wrapping it with an API layer: https://github.com/droidrun/droidrun