duo-mobile-engineering

Make a shipped client app start fast, stay small, and stay cheap to change — startup budgets scored against conversion rather than milliseconds, deferring non-first-screen work, perceived versus actual latency, device-tier and worst-region equity, profiling loops, binary size as a monitored metric, and how to migrate a large client codebase without freezing the product. Use when someone says the app feels slow, cold start takes too long, our binary keeps growing every release, users on cheap Android phones churn, CI builds take forever, should we migrate to a new language or architecture, how do we pay down client tech debt, who owns deleting legacy code, or why did our performance work not move a single metric.

Version

2.0.0

License

MIT