Supporting Asia and its millions of developers
summary
Asia contains as many unicorns as the West and shows rapid GitHub and Kaggle growth yet market data is inconsistent so count on local research. Developers skew younger and mobile-first market, many use older machines and unreliable internet so large SDKs fail. Localization pain points include Zawgyi script and Japanese date formats. Payment often uses carrier billing or vouchers. Outsourced teams prioritize speed and certifications over code quality. Prioritize regions by effort versus impact, ship tiny offline artifacts, and hire on-the-ground teams.
AI-written summary · about
chapters (17)
- 0:00Introduction and background
- 2:28DevRel fundamentals and roles
- 5:24Asia’s developer landscape
- 7:10Data accuracy challenges
- 8:16Cultural and technical barriers
- 10:01Mobile-first development trends
- 11:29Demographic differences in developers
- 13:37Chat-based applications and innovation
- 14:43Infrastructure and connectivity issues
- 15:23Learning preferences and education
- 16:47Outsourcing developer challenges
- 19:57Freelance developers in Asia
- 23:08Building for Asian developers
- 24:56Non-tech strategies for engagement
- 25:42Prioritization and local teams
- 26:45Feedback and advocacy
- 27:05Conclusion and future outlook
related talks
26mBuilding a Web3 Developer Ecosystem
53mWorldwide Python Communities: Learn From Organizers in Zimbabwe, Indonesia, and South Korea
25mWhat Developers Want
20mDevelopers are all the same - right?
59mLessons from Running Developer Platforms & Communities
26mSupporting SDKs in seven different languages while maintaining sanity
33mThe Power of Developer Communities
33mFireside Chat with Community Leaders in Singapore
