Form Factors #AskAndroid
summary
Advice is practical: use Jetpack WindowManager to read active display size, density and folding features rather than testing “isTablet” or “isFoldable”; adopt Compose incrementally (new UI components and future investments live there) — one team reports 30% engineering time saved porting to Wear; TV Compose alpha already ships lazy grids, featured carousel and immersive list; visual linting exists for XML and is coming for Compose; Now in Android demonstrates WindowSizeClass, nav rail and feed/list‑detail patterns; better large‑screen support drives higher engagement.
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
51mBuild Responsive UI in Android
26mMaking Apps adaptive with Material and Compose
02mTop 3 picks from the Form Factors track
28mBuilding an app for the Multi-Device world
18mCompose: Implementing responsive UI for larger screens
34mResponsive UIs for tablets, foldables, and other devices.
22mModern Android Development #AskAndroid