3 ms·
The missing piece here is the platform APIs. It’s less effort in UIKit to do swipe gestures and contextual menus than it is in the traditional Android APIs, so
by WoodenChair 4y ago
The missing piece here is the platform APIs. It’s less effort in UIKit to do swipe gestures and contextual menus than it is in the traditional Android APIs, so more developers do it. This equation may change with Jetpack Compose vs SwiftUI but I don’t have enough experience with Compose to say.
- rerdavies 4y agoOn Android, it is utterly trivial to do swipe gestures with RecyclerView, which is the current platform standard UI control for displaying lists (and has been for a long time). And context menus aren't particularly difficult either.
- kitsunesoba 4y agoAs someone who develops for both platforms I agree. Android Framework is just not as good as UIKit and may never be. Jetpack Compose does seem to be an improvement based on the dabbling I've done, but it's still a work in progress and there's no telling how long Google's interest in the project will persist. That said, as the sibling comment notes, swipe gestures and context menus aren't too bad to implement on Android. Like Gruber says, it's a cultural difference. For whatever reason it just doesn't strike the average Android dev that these features might be desirable.