Build effective OEM-level apps on Android Things
summary
Android Things is a managed variant of Android that grants permissions via the Android Things Console, not runtime dialogs, and often runs on ~512 MB devices so per-process heap is small (check ActivityManager.getMemoryClass). Best practices: split firmware into multiple APKs to avoid one-process heap limits, run the primary UI as the HOME activity that auto-restarts on boot, and connect background functionality with bindService from Application to protect it from the low-memory killer. Avoid BOOT_COMPLETED, START_STICKY and startService; use adb -g or Gradle installDebug to grant permissions and deploy modules.
AI-written summary · about
chapters (12)
- 0:00Introduction to Android Things
- 2:10Architecture Differences
- 3:05Handling UI and Permissions
- 5:20Development Best Practices
- 6:45Activity Lifecycle Management
- 9:07Memory Constraints and Tips
- 11:26Multi-Process Architecture
- 14:09Background Processes
- 16:37Bound Services for Stability
- 21:04Implementing Bound Services
- 23:05Android Studio and Tooling
- 25:49Review and Resources
