Research
Research from inside the ecosystem.
Field notes, ecosystem analysis, and operating research from the team working directly with developers, communities, universities, and technology platforms across India.
Understanding India's Developer Ecosystem
A practical view of how developers, communities, universities, and technology platforms interact — and what ecosystem teams should pay attention to when operating in India.
Field note · Ecosystem research
The research desk.
Notes on the systems behind developer adoption — community, universities, events, developer relations, and technology adoption.
- FIELD NOTE · OPERATING-MODELS-MODERN-DEVRELDeveloper RelationsR · 01Developer Relations
Operating models for modern DevRel.
Developer Relations works best when it is treated as an operating system for developer adoption, not as a collection of events, content campaigns, or advocacy programs.
Read → - FIELD NOTE · DEVELOPER-COMMUNITY-RETENTIONCommunityR · 02Community
The retention problem in developer communities.
Most developer communities do not have an awareness problem. They have a progression problem.
Read → - FIELD NOTE · CAMPUS-PROGRAM-ECONOMICSUniversitiesR · 03Universities
The economics of campus programs.
A university developer program should be treated as distribution infrastructure, not an event calendar.
Read → - FIELD NOTE · HACKATHON-CONVERSIONEventsR · 04Events
Why most hackathons produce nothing.
A hackathon can generate enormous short-term energy while creating almost no long-term ecosystem value.
Read → - FIELD NOTE · APPLIED-AI-BUILDERS-INDIAAIR · 05AI
India's applied AI builder cohort.
India's AI opportunity is not simply a story about the number of developers using AI tools. The more interesting question is how many developers are actually building and deploying AI products.
Read → - FIELD NOTE · CONTRIBUTOR-LADDERSOpen SourceR · 06Open Source
Contributor ladders that compound.
Open-source ecosystems become durable when they make the path from first contribution to trusted responsibility visible.
Read → - FIELD NOTE · WEB3-BUILDER-ADOPTION-POST-2024Web3R · 07Web3
Web3 builder adoption, post-2024.
Web3 ecosystem health should be measured through durable developer behavior, not attention cycles.
Read → - FIELD NOTE · FOUNDING-DEVREL-HIREDeveloper RelationsR · 08Developer Relations
The founding DevRel hire.
The first DevRel hire should not be treated as a communications hire. It is an ecosystem operating role.
Read →
What we keep noticing.
Patterns become useful when they change how a program is operated. These are the recurring observations behind our work.
- 01Observation
Local context changes adoption.
The same platform can behave differently across cities, communities, and university environments. Distribution is rarely uniform.
- 02Observation
Participation is not adoption.
Registrations, attendance, and impressions are useful signals — but sustained developer activity happens later.
- 03Observation
Continuity beats isolated launches.
Communities, campus programs, and developer relationships become stronger through repeated operating cycles.
- 04Observation
Research should change the work.
The value of ecosystem intelligence is not the report itself. It is the decision it helps an operator make.
One useful note, once a month.
New field research, ecosystem observations, and the occasional number worth paying attention to.
Delivered by Substack. One email a month. Unsubscribe in one click. Open on Substack
Have an ecosystem question?
Bring us the question behind the numbers. We use field experience, ecosystem research, and operating context to find the useful answer.