---
tags: 0x
---

# 0x Developer Community Audit

:::success
## Audit of 0x Developer Advocacy
::::


0x should create retaining walls minimize participant drop-off

### What does success look like
- :star: API metric, market share of decentralized exchange vol that's attributable to 0x's API
- what's the current and what's the goal?
- individual devs contribution is near 0, most is institutional
- Matcha, how much are these products producing vol
- with every dev we adopt, which one has the most vol contribution
- open to expanding the defintion of metrics
- devs are existing companies may improve their company
- metamask, many users, swap functionality
- open repo, don't have a lot of external contributors
- ie more vol of individual contributors
- our approach do we build our own devs beyond leveraging other projects' devs
Two theories
- our tech is too intimidating
- we don't expose PRs that others can work on
Potential messaging pivot of open-source vs corporate

### What is working

Discord - top of funnel works really well. 

Discord is the platform to catch and engage the devs.

technical-help

API help has an idea in mind

Defi Academy - teams to work with

Well organized, users seem to know where to go

Brent most proud of: content, blog consistency

Reddit - more general audience

Converting web2 devs to web3

### What is not working

 1. [PROCESS] who/why/how did they join, when a dev reaches discord, we don't know where they came from, what are they looking for
 2. [LOGISTICS] bandwidth, limited resources, same eng building the product is helping the devs in the community
 3. [PROCESS] docs with starter guides, some are outdated, some Qs are very basic, as if no one even read the documentation
     -our technical docs - current engineers are the technical writers
 4. [LOGISTICS] Support functions broken: we have devs coming from multiple channels, how do we fix it, as if devs go to the most sense, set up a private channel on Telegram 
     - have not directed to specific channel for support, some niche questions are private, needs for private & public channels
     - chat is not support for scale, issue tracker
**our customers are our users, we need to give them a great experience and priority
5. [LOGISTICS] Finding the right dev for the project
6. [LOGISTICS] limited bandwidth for hackathons, high touch engagement activity
7. [PROCESS] two sides of the equation for dev acquisition, why are we not investing top of funnel of dev acquisition, ability to address that demand to generate it, get folks into the funnel, integrated to 0x, and disjointed at this stage
8. [PROCESS] how for community members to give back
9. [LOGISTICS] Potential messaging pivot of open-source vs corporate
 

---