Android automation is easier to reason about when it starts from the screen.
That sounds simple, but it matters. A lot of mobile work does not happen through a clean backend API. The useful state is often visible: a button appears, a search result loads, an error toast disappears too quickly, a translated label overflows, or a permission dialog changes the next step.
For QA, support, e-commerce operations, and app teams, the repeated work usually looks like this:
open an app
wait for a screen to load
