For an app having its own custom design system and...
# compose-android
n
For an app having its own custom design system and UI library implemented in view-based UI, according to migration strategy recommended here at https://developer.android.com/jetpack/compose/migrate/strategy#build-new, we should allow views to co exist with Compose. But due to inter-op bug around hardware keyboard navigation (https://issuetracker.google.com/issues/255628260), apps which needs to support all a11y needs (including hardware keypad support) are currently blocked on adopting Jetpack Compose. The issue was raised in
Oct 26, 2022
, With this issue being open, also wondering how Jetpack Compose for Android TV is being adopted given the h/w keypad navigation is essential for apps to migrate. Can someone from Compose team share any update on whats the priority for Compose team to address this issue.
­čĹÇ 1