- \n
- Getting Noticed<\/strong>. We began BD outreach to a dev tool influencers and authors who compile \u201cdev tool lists.\u201d This week, Sidekik was listed on the ConsenSys Dev Tool<\/a> and the Ethereum Classic Dev Tool<\/a> lists.<\/li>\n\n\n\n
- Engaged User Sessions<\/strong>. User analytics show that some users spend 60+ minutes per session, while the average session is closer to 13 minutes. We\u2019re pondering, \u201chow do we turn those users into advocates?\u201d Your ideas are welcome.<\/li>\n\n\n\n
- Feedback & Support<\/strong>. We added Intercom to capture feedback and offer support. One user already suggested a useful feature: saving contracts that they interact with frequently, because contracts currently disappear upon refreshing the page.<\/li>\n<\/ul>\n\n\n\n
Challenges<\/h3>\n\n\n\n
- \n
- Sync Directory Feature<\/strong>. It seems most users do not save their contract address and ABIs to a local file, preferring to onboard via our \u2018sync directory\u2019 feature. Reading every file in the browser\u2019s main thread, however, was a painfully slow user experience. We updated our code this week, and we\u2019re now delivering a much faster experience.<\/li>\n\n\n\n
- Onboarding.<\/strong> Some devs did not successfully onboard last week. Sidekik was built as an internal tool for users who had prior knowledge of how to setup and get value. Obviously, that\u2019s not the case for a random developer coming to the web app for the first time. We see that stuck users read the browser\u2019s console logs, and so we updated the error messages there to provide more onboarding guidance. Second, we fixed a bug where people uploaded ABI files first and then connected a chain, which caused the UI to enter a glitchy loop:<\/li>\n<\/ul>\n\n\n\n
![\"\"\/](\"https:\/\/cdn-images-1.medium.com\/max\/800\/1*bHUYN6nqqs9c6-kqUI7yxQ.gif\")
<\/figure>\n\n\n\nAsks<\/h3>\n\n\n\n
- \n
- ETHDenver.<\/strong> We submitted applications to speak at ETHDenver<\/strong>. If you have any connections to that speaker selection committee, I’d love an assist there.<\/li>\n<\/ul>\n\n\n\n
\n\n\n\nThank you for reading and following our journey \ud83d\ude4f<\/p>\n","protected":false},"excerpt":{"rendered":"
Startup Retro, 12\/4\u201312\/11 The last week just flew by! We were heads down on improving the onboarding process for developers, as we aim to shorten the usage-feedback-iteration flywheel. Read on to get a quick summary on our highlights, challenges, and asks. In particular, if you know anyone at ETHDenver, I\u2019d love an assist on getting …<\/p>\n
- Onboarding.<\/strong> Some devs did not successfully onboard last week. Sidekik was built as an internal tool for users who had prior knowledge of how to setup and get value. Obviously, that\u2019s not the case for a random developer coming to the web app for the first time. We see that stuck users read the browser\u2019s console logs, and so we updated the error messages there to provide more onboarding guidance. Second, we fixed a bug where people uploaded ABI files first and then connected a chain, which caused the UI to enter a glitchy loop:<\/li>\n<\/ul>\n\n\n\n
- Engaged User Sessions<\/strong>. User analytics show that some users spend 60+ minutes per session, while the average session is closer to 13 minutes. We\u2019re pondering, \u201chow do we turn those users into advocates?\u201d Your ideas are welcome.<\/li>\n\n\n\n