Our picker looks native on iOS and can be customized to look more native.
It's more functional than the native picker and doesn't have as many
issues. If there's an issue with the L or functionality in the the
lightweight picker we need to address that issue, not the "nativeness"
which as I
I don't know why the OP need native pickers, but from my perspective iOS
users expect consistency and don't understand why an iOS app would not use
native pickers as probably 99% of all apps do. iOS users basically don't
care about developer considerations and CN1 limitations. I had this
