IO: Developer Experience Initiative
248 DReps voted · 94 with a rationale · 18 changed their vote
Open a row to read the rationale.
- Yes128K ₳No rationale
- Yes120.3K ₳No rationale
- Yes118.7K ₳Rationale
I am voting yes because I view developer experience as one of the most immediate barriers to Cardano’s ecosystem growth. Infrastructure and scaling investments only realize their potential if developers can efficiently build, experiment, and deploy applications.
Cardano’s fragmented tooling, scattered documentation, and steep learning curve create friction for both new and experienced builders. I support efforts that reduce these barriers through improved onboarding, standardized patterns, simplified setup, unified documentation, and reusable contract libraries.
My support is not an endorsement of every tooling initiative. I remain mindful of overlap with other proposals, but view this one differently because it focuses less on deep protocol refinement and more on practical builder accessibility.
I believe reducing time-to-first-project and improving developer retention may provide a more direct path toward ecosystem growth and adoption. While ambitious growth targets should be evaluated critically, improving the builder experience addresses a current constraint rather than a future one, making this a worthwhile investment in Cardano’s long-term utility and resilience.
- Yes115.6K ₳No rationale
- Yes110.9K ₳No rationale
- No108.3K ₳Rationale
I am voting against the Developer Experience Initiative at this time. While developer onboarding is important, Cardano is currently in a critical infrastructure growth phase where resources must be prioritized toward the features that make our network distinct: high assurance, formal verification, and high security.
Advanced builders and enterprise partners are more concerned with throughput, security guarantees, and uptime than they are with simplified UI/UX tools.
I believe this initiative is mistimed. The treasury should remain focused on the vital technical upgrades required to scale the network and prove its security guarantees. - Yes107.2K ₳No rationale
- Yes95.4K ₳No rationale
- Yes92.6K ₳No rationale
- Yes89.9K ₳No rationale
- Yes85.7K ₳No rationale
- Yes64.4K ₳No rationale
- Yes59.8K ₳Rationale
I am voting YES on the IO: Developer Experience Initiative.
This proposal stands out because it draws strong attention to new opportunities in the ecosystem. Cardano already has a robust and secure infrastructure, but it was missing exactly this kind of practical incentive to attract and retain more developers.
With the proposed improvements — such as the cardano-init CLI, the OpenZeppelin-style smart contracts library, the unified Developer HUB, and bounties for existing tools — many new developers will be encouraged to join the network. These developers will build high-quality dApps, bringing more liquidity, more users, and real activity to Cardano.
This is a smart investment that accelerates the ecosystem flywheel and is fully aligned with Cardano’s 2030 goals for Adoption & Utility. The requested amount is reasonable, the management through Intersect is transparent, and the potential return for the network is significant." - Yes59.6K ₳No rationale
- Yes52.4K ₳No rationale
- No50.5K ₳No rationale
- Yes49.7K ₳Rationale
I vote YES with accountability expectations. Cardano needs convenience without dependency. This proposal can reduce developer friction through shared tooling, better onboarding, reusable contracts, bounties, and measurement — all of which can strengthen ecosystem capacity if delivered openly and collaboratively.
My support is based on the expectation that the work is upstreamed where possible, coordinated with existing maintainers, transparently reported, and measured against real DevX outcomes. Treasury funding should not create permanent dependence on IO or any single provider. It should make Cardano easier to build on while increasing the capacity of the whole ecosystem. - Yes49.6K ₳Rationale
I shall continue to vote in favor of the Input Output Global (iOG formerly known as iOHK) proposals due to the fact that iOG has continuously year in and year out built, upgraded, innovated, and further strengthened the ecosystem through various market upheavals, negative press, and technological shifts. Through continuous efforts this cadre of developers, educators, various business persons, scientists, and experts in their fields have proven more than capable of the continued maintenance and innovation necessary to further the Cardano blackchain. I find value in all proposals from iOG until a suitable development group or lab can prove not only innovative, but evolutionary for the technology in which we all utilize and enjoy. The blockchain has survived based off of the creators of the protocol, we must continue the path set forth until we have a suitable substitute that can create viable upgrades and are capable of pushing the community and the blockchain into a realm of technological dominance I vote Yes for this proposal.
LourdeOuroborus Imperator Aeternalis - Yes46.5K ₳No rationale
- Abstain45.2K ₳No rationale
- Yes40.5K ₳No rationale
- Yes39.7K ₳No rationale
- No36.3K ₳Rationale
Why is an additional ₳3 million being requested now for Developer Experience when we already voted for ₳130,708,860 before?
Was this not included in the original ₳131 million budget? Also, only ₳78 million has been used so far, so why is more funding needed now?
- Yes31.9K ₳No rationale
- Yes29.3K ₳No rationale
- No26.7K ₳Rationale
It will fail if done with Intersect. No.
- Yes25.7K ₳No rationale
- Yes15.9K ₳No rationale
- No15.3K ₳No rationale
- YesRevoted15.2K ₳History
Earlier votes
Yes2mo agoSuperseded
- Yes12.9K ₳Rationale
I believe that io has the best interest of the cardano blockchain at heart.
- Yes11.3K ₳No rationale
- Yes9K ₳No rationale
- Yes8.1K ₳No rationale
- No6.7K ₳No rationale
- Yes4.4K ₳No rationale
- Yes2.4K ₳No rationale
- Yes1.7K ₳No rationale
- Yes1.6K ₳No rationale
- Yes1.2K ₳No rationale
- Yes997 ₳No rationale
- Yes684.4 ₳No rationale
- Yes682 ₳No rationale
- Yes340.7 ₳No rationale
- Yes84 ₳No rationale
- Yes11.9 ₳No rationale
- Yes0 ₳No rationale
- Yes0 ₳No rationale