Elements That Appear in Android Project Estimates, or Carefully Buried Landmines
summary
This talk explains common hidden factors that break Android project estimates: design handoffs arriving as PSDs instead of Android assets, custom iOS UI requiring extra implementation, and SNS integration needing full in‑app posting rather than simple intents. It also covers technical pitfalls like GPS noise breaking 10‑meter proximity features (requiring beacons or server smoothing), CI/ops overhead from CircleCI/Jenkins and Gradle breakages, and long build times ballooning to 40–50 minute cycles that stall releases.
AI-written summary · about
chapters (10)
- 0:00Android project estimates
- 2:35Estimate assumptions
- 8:17GPS accuracy pitfalls
- 11:27App startup behavior
- 15:37CI pipeline costs
- 18:25Human factors in estimates
- 21:19Technology selection
- 24:50Team dynamics risks
- 28:46Quality vs deadlines
- 30:11Q&A
related talks
01h 00mAndroid at Scale
22mFrom Chaos to Control: Future-Proofing Your Android Release Process
55mSynthesis of Modern Quality Criteria for Android Apps
33mTackling Tech Debt on Android
26mEfficient Android Builds at Scale: Lessons from Pinterest
27mDeveloper Experience: It’s Time to Start Complaining
31mImproving Android Build performance
01h 10mWhy Projects Succeed: Lessons learned from the Android OS