The introduction of a Product Org is an excellent development, as it focuses on user needs and ensures feedback is funneled across all teams, making Radicle truly user-centric and hopefully helping towards its broader adoption. I also appreciate the distinct value propositions for different customer segments—companies and individual developers. It makes sense to cater to these groups separately since their needs vary significantly.
However, one thing is unclear to me: do we have evidence that individual contributors prefer to onboard to Radicle and access its services via a desktop client rather than through tools they already use, like their editor or IDE (e.g., Neovim, VSCode, IntelliJ)? Maybe it’s me but, I couldn’t find any validation supporting this approach.
In my experience, it’s usually harder to change user habits by asking them to install and adopt a new application compared to adding a feature within tools they already use. It might be worth the time to ask individual contributors directly to validate this assumption. What are their current workflows, and would they find more value in a desktop client or an integration within their existing development environment or maybe both?
This is similar to what you’ve already done with companies. Interviews and surveys clarified that companies don’t just need a code hosting service—they also require a CI tool, as it’s a fundamental part of their workflow. This insight shaped the offering to better meet their needs. I propose that part of the Product Org’s job is to validate assumptions regarding the preferred touchpoints for individual contributors. Understanding where and how they prefer to interact with Radicle could significantly enhance adoption and overall user satisfaction.