Form Factors #AskAndroid
summary
Recommends using Jetpack WindowManager to read active display metrics and detect folding features rather than checking “is tablet/foldable,” and to use WindowSizeClass and canonical layouts (notably list-detail versus supporting panel) for large screens. Advises migrating to Compose incrementally since future UI components and tooling (including Compose on Wear and TV alpha components like lazy grids) land there; Wear auth works best when phone and watch share the same package so tokens can be transferred.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:31Questions
- 2:47Compose adoption story
- 5:52Authentication
- 7:39Onboarding Screen
- 8:20Challenges
- 10:32Best large screen experiences
- 11:27Visual linting
- 12:39Canonical layouts
- 14:18Android Auto vs Android Automotive
- 16:25Wear OS
- 17:57Android with large screen
- 19:12Conclusion
related talks
21mForm Factors #AskAndroid
26mMaking Apps adaptive with Material and Compose
51mBuild Responsive UI in Android
01h 01mComposing large screens
34mResponsive UIs for tablets, foldables, and other devices.
47mThe age of large screen & foldables
28mBuilding an app for the Multi-Device world
20mDo’s and don’ts: Mindset for optimizing apps for larger screens