A mobile test automation framework that passes sequentially and collapses under parallel execution isn't flaky. It's single-threaded by construction — one driver instance, screen objects holding element proxies bound to that driver, every thread targeting the same device and the same automation port. That's an architectural problem, not a matter of tuning waits. I spent the last few months building one in Java and writing up each step. Nine parts, one codebase, starting from an empty direc...