I'm not an expert on Orbot but in which case and how could an IP leak using Orbot, assuming Orbot routs all the activated app's communication only over TOR? And how can an app developer fix this reliably? And how can the user know the client dev fixed it reliably 100% all the time with every update? I'm talking out of the experience where an app used an installed Orbot to talk to some servers then a new dev team introduced other servers but did not care about using Orbot when the still available TOR option was activated, misleading the user to assume to be private where they are not.

Orbot utilizes android's VPN API so I assume it controls the full applications network stack (or full device if configured that way). Still I think androids VPN stack has some holes. @Vitor Pamplona Can the in-app component cooperate with an ambient orbot? Best of both worlds?

rely on orbot as proxy put pretty the same trust in app devs not leaking ip. Using it with orbot as vpn put this trust into the os.

You shouldn't give privacy advice if you don't know what you're talking about.

Orbot always breaks for me

It depends on whether Orbot is used as a VPN or as a proxy. In the former case, the application cannot escape Tor, in the latter case it can of course, avoiding using the proxy. So Orbot as VPN is safer than current Amethyst's implementation, while the new built-in support has the same robustness, but avoid a dependency and all the troubles related to the configuration, offering a better experience to the user.

It would be useful to have an indicator in the app whether it's on tor or clearnet, so I can be sure about what connections I'm using.

It's likely going to be using both at the same time for the vast amount of users.