Most flaky mobile tests are locator debt, and the fix sits upstream of the suite

Every tier in that ranking is really an answer to an ownership question. Take the three ways the author says an accessibility id goes bad: a generated value like `button_3f9a`, one value reused down a list, or a TalkBack sentence sitting in `contentDescription` that changes with the locale ^[8]. All three are values chosen in application source, so the durable repair is a commit in the app rather than an edit to the suite ^[20]. His remedy for the third case, ask for a `resource-id` and leave `content-desc` to accessibility ^[8], is a ticket on somebody else's board.

The write-around, when you need one, has a shape. Where an ID lives inside a reused component and twenty rows share it [c11b], the advice is to add a second condition rather than drop to XPath by index ^[12]: the shared ID plus that row's label narrows to one element without touching the hierarchy ^[15]. Text is a poor primary anchor outside a single-language app with no near-duplicates on screen ^[13], and a decent qualifier, because both halves of that locator still point at something a person typed deliberately ^[4].

On iOS the same logic applies to the fast native options. Predicate strings and class chains are XCUITest queries, materially quicker than XPath on a deep tree, one filtering on attributes and one navigating the tree ^[16]. Their failure modes travel with the syntax. A predicate on `label` dies with localisation, which is why the author filters on `name`, the accessibility identifier ^[17]; the same release that turns "Continue" into "Nastavi" for Serbian takes out every text locator too ^[14], so one line in a changelog retires two strategies ^[21]. A class chain carrying an index breaks when a cell gains a child ^[17], the same trigger as the path an inspector hands you when you click copy XPath ^[18].

Which is why the author puts the long-term fix outside the test repo entirely: get IDs added where the feature is written ^[19]. An `android:id` costs a line in a layout file, is never shown to a user, and changes only when someone renames it on purpose ^[9]. Without it, the suite's break schedule is set by whoever next refactors a layout, swaps a design system component, or ships an OS that renders a control differently ^[5], and none of those people will open the test.