can't you position one bike facing forward and one facing back, so the handlebars don't collide? Either way, going with an absurdly big and dangerous car to avoid _awkwardly positioning_ some cargo is pretty American thing to do

Do you have any sources for this? I looked online and found a couple of charts, none of them support this claim. The Ford Ranger sales in Europe vs US are similar (who buys more varies by year) but the F series seems to be mostly bought in US

Other than that, some popular and useful libraries will bundle native libs (for example for sql), and some ad/analytics/corporate SDKs will use native libs to share code between platforms and for obfuscation. These corporate SDKs (like Zendesk) will also notoriously break Android minification tools, because why bother

I now see the article is about iOS app, but it looks like the Android app is anywhere between 50mb and 100mb (depending on the apk download side I look at) which is much more reasonable

There's an exception for banking apps

> Apps that have a verifiable core purpose facilitating financial-transactions involving financially regulated instruments (for example, dedicated banking, dedicated digital wallets) may obtain broad visibility into installed apps solely for security-based purposes.

But HSBC app declares "" permission, which requires an explicit approval (https://support.google.com/googleplay/android-developer/answ...) but

> Apps that have a verifiable core purpose facilitating financial-transactions involving financially regulated instruments (for example, dedicated banking, dedicated digital wallets) may obtain broad visibility into installed apps solely for security-based purposes.

The other way around — make it clear that the devices are capable of showing ads, and provide instructions on how to opt-in to them (and no cookie-like prompts either)

- there's no touch feedback (ripple) on many of clickable components. Some that do have it look non-native, inconsistent and sometimes gets stuck

- the search bar on top app bar in `search` tab looks very non-native and non-standard (it's elevated on top of elevated app bar already)

- the lists look iOS-y, especially settings

- the settings list item has weird glitch where it loses background after touching (but not clicking)

- collapsing comments is pretty choppy (on a Samsung S25 so a pretty powerful phone)

- can't swipe down a bottom sheet (with post options/actions)

- it's just not android-y — the navigation is weird, the design is all over the place,

It's not unusable and it's a good tradeoff for a small team I guess. But this is nowhere near the experience a native app can provide, and has lots of small papercuts that would make for at least a slightly frustrating experience. It is a decent app don't get me wrong, but it's clearly not native

There's some jump from _a property exists_ to _it must be used_, but a massive one from _a property exists_ to _Apple uses it everywhere and we never notice it because they are done well_.

On mobile the webview app experience is crap and it's immediately obvious that an app is not native. Simply nobody asks customers how they like it. The management assumes that as long as nobody complains and the users don't leave in droves, the experience must be impeccable.