Developers need to keep in mind that the target area for the URL bar is much larger than the env(safe-area-inset-bottom) suggests and in my testing might be dep

Developers need to keep in mind that the target area for the URL bar is much larger than the env(safe-area-inset-bottom) suggests and in my testing might be dependent on how an interactive element is placed (e.g. position sticky, fixed or freely flowing). In my testing, to prevent the URL bar from showing or needing the user to double-tap, a 44px height button needs an additional bottom margin of at least 30px + env(safe-area-inset-bottom). That's pretty high up from the bottom. And... you need an actual device to test these tap issues out reliably.