I have to say reading the statement "requires some pretty aggressive permissions to work" sounds like there's a problem with Android permissions model. I mean, if the app needs permissions, one should normally assume it needs these permissions in order to, well, be permitted to do its work? In other words, a "good-natured" app should not need more permissions than it needs to work, and the last part is kind of a tautology. Either that, or Android has broken permissions model, which may apparently be too coarse -- as in you need "access to Internet" for auto-update to work, despite auto-update normally being done by Google (when a Google-forked Android) over a secure channel etc.
I agree about the principle of least privilege, but the problem is that almost any accessibility app must basically be able to simulate user input to function, i.e. for a cursor app to actually provide a cursor, it must have the permission to activate any UI element on the screen.
I trust Quick Cursor, but I shouldn't have to - since basically every smartphone now is too big to use with one hand without having to shuffle it around and risk dropping it, I think the cursor feature should be built into the OS.
