does anyone have any suggestions on approaches on ...
# android
j
does anyone have any suggestions on approaches on how to handle navigation for apps using both phone and tablet layouts?
stackoverflow 4
google 3
k
1. checkout constraint layout. 2. Someone is probably going to tell you that's not kotlin specific so not appropriate for this Slack.
m
Separate xml for tablet/phone - use navigation component from jetpack.
j
I should have asked the question better. If I am using something like a master /detail layout navigation doesn't cover that.
i
master/detail wouldn't need navigation. Detail would need some kind of FrameLayout.