The State of Mockodile in 2018
summary
Android customization becomes the growth engine and the headache: community distributions like CyanogenMod-driven OnePlus launch prove grassroots ROMs can ship features and users, while chipset vendors such as MediaTek reference ROMs causing update gaps leave many devices unpatched and buggy. Fragmentation shows up as unreproducible crashes on tiny market-specific phones. Use analytics and crash SDKs to locate affected models, decide to remove broken features when data supports it, and prefer market-specific builds only when necessary.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:05What is Mockodile
- 7:26Android customization history
- 10:16Android fragmentation explained
- 12:42CyanogenMod community impact
- 17:02iOS vs Android update issues
- 19:08Affordable Android devices
- 20:36MediaTek and market dynamics
- 23:10Android development challenges
- 25:22Analytics and prioritization
- 27:09Community-driven features
- 28:24Fragmentation vs control
- 31:13Market-specific strategies
- 33:51China’s platform agnostic shift
- 35:27Developing for China
related talks
23mAre Bad Manufacturer Overlays a Thing of the Past?
46mMod your Android
33mBust the Android Fragmentation Myth
37mA Developer's Diary: The Trials and Triumphs of Maintaining Devboards in AOSP
01h 08mAndroid Plateform Anatomy
45mThe Unyielding Spirit of Android
20mAndroid is open source, what does that mean for us?
40mChallenges of an open source operating system