hirosystems/hiro-experience-map

An interactive map of the Hiro Developer Experience

Stars: 0
Forks: 0
Open beginner issues: 0
Indexed issues: 57

Dominant language: TypeScript
License: No license data
Last GitHub push: Apr 8, 2025
Latest indexed: Sep 17, 2026
Contributing guide: No contributing guide
Code of conduct: Code of conduct
Beginner labels: No beginner labels indexed
PR merge metrics: No merged PRs in 30d

Open All

57 issues indexed so far

Social signals (influencers, crypto twitter, token price, etc.) obscure the true potential and utility of various blockchain protocols and technologies. Open

Social

hirosystems/hiro-experience-map#1 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Inconsistent placement and treatment of resources between Hiro Docs and Platform (eg Guides, Recipes, Templates) Open

Docs Examples & Guides Platform Templates

hirosystems/hiro-experience-map#3 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Hiro / Stacks documentation and educational resources don’t provide a clear progressive learning path for new developers. Open

Docs

hirosystems/hiro-experience-map#4 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Certain primitives (oracles, price feeds, etc) may not be available for developers looking to compose applications without having to reinvent the wheel. Open

Primitives

hirosystems/hiro-experience-map#5 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Project templates are not accessible outside of the Platform. Open

Clarinet Platform Templates

hirosystems/hiro-experience-map#6 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Platform exhibits poor usability and experience design for many of its core features (eg Chainhooks, Monitoring, Devnet) Open

Platform

hirosystems/hiro-experience-map#7 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Lack of accessible tooling to enable smart contract / transaction simulation and cost analysis. Open

Clarinet Platform Simnet Simulation

hirosystems/hiro-experience-map#8 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Available resources assume developers possess a certain understanding of blockchain fundamentals. Open

Docs Hiro.so Stacks.co

hirosystems/hiro-experience-map#9 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Platform features exist in isolation rather than functioning in unison to power projects. Open

Clarinet Platform

hirosystems/hiro-experience-map#10 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Available examples and use-cases fail to adequately showcase one of our core value props: sBTC Open

Docs Examples & Guides Hiro.so Platform

hirosystems/hiro-experience-map#11 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
When first encountering Stacks & Hiro, developers are unsure of what’s possible, or how Stacks & Hiro’s primary differentiators directly affect the developer experience or potential outcomes. Open

Examples & Guides Hiro.so

hirosystems/hiro-experience-map#12 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Fragmentation of content and resources across Hiro and Stacks Foundation properties. Open

Blog Docs Hiro.so Stacks.co

hirosystems/hiro-experience-map#13 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
It’s difficult to learn multiple technologies simultaneously (Stacks, Clarity, Bitcoin, etc). Open

Docs Hiro.so Stacks.co

hirosystems/hiro-experience-map#14 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Lack of multi-chain interoperability. Open

hirosystems/hiro-experience-map#15 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Second-class (or non-existent) treatment and support for some of Hiro’s primary differentiators such as Post-Conditions (are there others?). Open

Docs Hiro.so Platform

hirosystems/hiro-experience-map#16 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Overwhelmed by the sheer quantity of Resources to consult between Hiro & Stacks. Open

Docs Hiro.so Stacks.co

hirosystems/hiro-experience-map#17 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Developers coming from other protocols/ecosystems struggle to understand which tools and solutions may be analogous to those with which they are already familiar. Open

Docs Hiro.so

hirosystems/hiro-experience-map#18 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Lack of intentionally designed transitions or handoff between our core products in order to push developers towards the next logical step in their developer journey, or to encourage the use of particular Hiro tools/services at each stage. (eg Docs → Playground, Docs → Platform, Playground → Platform) Open

Clarinet Docs Hiro.so Platform

hirosystems/hiro-experience-map#19 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Writing Clarity presents a steep learning curve. Open

Clarity Clarity Playground Examples & Guides

hirosystems/hiro-experience-map#20 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Documentation examples are sometimes broken or incomplete. Open

Docs

hirosystems/hiro-experience-map#21 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Lack of best practices for testing smart contracts. Open

Clarinet Docs Platform

hirosystems/hiro-experience-map#22 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Lack of production-ready guides to aid developers in the transition from experimentation to building production ready applications. Open

Docs Examples & Guides

hirosystems/hiro-experience-map#23 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Devnet is challenging to use and challenging to understand for new users Open

Devnet

hirosystems/hiro-experience-map#24 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
For new developers, it is often unclear which tools to use at which stage of development Open

Clarinet Docs Examples & Guides Platform

hirosystems/hiro-experience-map#25 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Unclear which external protocols, contracts, and features may benefit my project. Open

Docs Examples & Guides

hirosystems/hiro-experience-map#26 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Initial installation and developer environment setup can be challenging. Open

Clarinet Docs Examples & Guides Platform

hirosystems/hiro-experience-map#27 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Lack of parity between the Clarinet and Platform Developer Experience. Open

Clarinet Platform

hirosystems/hiro-experience-map#28 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Devnet suffers from poor reliability and performance. Open

Devnet

hirosystems/hiro-experience-map#29 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
We (Hiro) lack sufficient insight around when/where developers are getting frustrated or abandoning our tools/services. Open

Usage & Analytics

hirosystems/hiro-experience-map#30 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Content & Documentation are often out of date. Open

Docs Hiro.so

hirosystems/hiro-experience-map#31 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Referencing and navigating docs during development requires a lot of context switching that can result in a loss in productivity and efficiency. Open

Clarinet Docs Platform VSCode Extension

hirosystems/hiro-experience-map#32 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
No easy way to search through all available resources and documentation to seek answers to specific problems or challenges. Open

Docs

hirosystems/hiro-experience-map#33 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
It’s difficult to build confidence around the resilience and security of my smart contract applications before deploying to mainnet. Open

Platform Security

hirosystems/hiro-experience-map#34 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Difficulty understanding the cause of failed transactions Open

Explorer Platform

hirosystems/hiro-experience-map#35 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Lack of dedicated and reliable support channels for when issues arise during development Open

Support

hirosystems/hiro-experience-map#36 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Lack of clear and strong distinctions between Devnet / Simnet / Testnet as it relates to the problems they solve for developers and the best practices for their use during development. Open

Devnet Docs Platform Simnet Testnet

hirosystems/hiro-experience-map#37 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Frustrations with available tooling and support for testing and debugging smart contracts. Open

Clarinet Platform

hirosystems/hiro-experience-map#38 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Developers are not always aware when a solution or tool may exist for a problem they are encountering. Open

Clarinet Docs Platform

hirosystems/hiro-experience-map#39 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Lack of guidance, tools, and resources for developers looking for smart contract security audits. Open

Platform Security

hirosystems/hiro-experience-map#40 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Successful troubleshooting is often reliant on developers’ ability to unearth the relevant information from a variety of resources and documentation. Open

Docs Platform VSCode Extension

hirosystems/hiro-experience-map#41 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Mainnet deployment can be challenging and stressful, since Mainnet deployments and transactions are immutable. Open

Clarinet Mainnet Platform

hirosystems/hiro-experience-map#42 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Lack of zero-config, real-time notifications triggered by chainhooks / monitoring tools. Open

Chainhooks Contract Monitoring Platform

hirosystems/hiro-experience-map#43 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Lack of guidance around requirements for hosting a decentralized application (In contrast to Web2) Open

Docs Mainnet

hirosystems/hiro-experience-map#44 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Lack of analytics/tools to enable developers to monitor the usage of their applications. Open

Platform Usage & Analytics

hirosystems/hiro-experience-map#45 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
We (Hiro) lack a perspective on which monitoring tools developers need to power early vs late-stage development. Open

Contract Monitoring Usage & Analytics

hirosystems/hiro-experience-map#46 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Developers have no convenient way to monitor their API usage and rate limits. Open

APIs Platform Usage & Analytics

hirosystems/hiro-experience-map#47 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Developers lack sufficient avenues for getting feedback on the things they are building. Open

Support

hirosystems/hiro-experience-map#48 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Inability to check logs for individual Chainhooks. Open

Chainhooks Platform Usage & Analytics

hirosystems/hiro-experience-map#49 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Inability to activate/deactivate different chainhooks and contract monitoring instances without removing them entirely. Open

Chainhooks Clarinet Contract Monitoring Platform

hirosystems/hiro-experience-map#50 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026
Inability to organize various API keys / Chainhooks / Monitoring instances based on the projects I’m building (Current experience is a catch-all). Open

Chainhooks Contract Monitoring Platform

hirosystems/hiro-experience-map#51 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

A short digest of beginner-friendly GitHub issues.