Continuing to Improve the Kin Developer Experience (Part II)
Last week, we published a post discussing the principles and reasonings behind improvements being made to the Kin developer experience, “Enhancing the Kin Developer Journey“.
When approaching a new code base or system, there’s a lot that one must hold in their head at once. The more variables one is forced to hold, the less likely they are to enjoy the process or meet success. Having to bounce between multiple sites, brand experiences, and writing styles drastically increases those variables — cognitive overhead — and the time one has to spend getting their code to work.
For wonderful reasons ranging from the community driving tutorials and starter-kits to Kin Foundation making quick improvements and updates, Kin’s docs, tutorials, SDKs, starters, and portal ended up being spread across too many domains. It was a rather fantastic problem to have, but it needed to be fixed. Open source is great, but also messy at times.
We set a goal of wrangling our docs, Bram Borggreve’s huge contributions to the community on Kintegrate.dev, and our new lander into a unified property as soon as possible. We felt the best path was to just get that unified site done, even if it meant including the legacy issues, typos, mistakes, alternative styles etc… Once released, we could begin the longer term work — an ongoing task — of improving and simplifying what exists.
I’m pleased to say that it’s been a busy and productive few days since our last announcement, we achieved that rather mammoth goal in only one week thanks to everyone at Kin being willing to get their ‘hands dirty’. It was an all team effort ranging from the Developer Relations team setting up, porting in, and testing to the comms and Business Development teams helping us double check linking and device support.
You can check out the integrated site and help further our ‘bug hunt’ by going to the docs.
Important things to note:
- developer.kin.org is our new Developer Experience home base — bookmark it and help spread the word!
- Of course, there are opportunities to improve. This is only a step in the right direction, not a completed journey.
- Although Kin’s digital properties will immediately point to the new docs site, docs.kin.org and kintegrate.dev will be left up for 30 days to allow anyone who is more comfortable with the legacy sites ample time to make adjustments.
- After 30 days, redirects will be set-up that — in most cases — will ensure bookmarks and backlinks point to the same relative information.
- We’ve removed the “Deprecated” and “Migration to new SDKs” sections of the docs on the new site. The information there is no longer relevant but is a cause for confusion for new developers who find those pages in search engine results. If, for some reason, there is information you find valuable there, you’ll have 30 days to screen-shot or record from the old docs site.
If you’re a developer and have thoughts, suggestions, would like to raise an issue, or want to be a contributing member of an amazing community creating the easiest, quickest, and most intuitive way of integrating cryptocurrency into app experiences, then don’t wait … come join us. Your starting point is: Developer.Kin.Org.
Kin is a decentralized cryptocurrency purposely designed to integrate easily across Mobile and Web Apps, with a built-in incentive model that rewards developers for increased usage. Apps built with Kin get paid for creating compelling cryptocurrency-based user experiences, where greater engagement results in shared economic benefits for users and developers. Today, the Kin Ecosystem boasts 60 million wallets, and has distributed over $70M in rewards across 60+ apps since its inception in 2017. Kin is an SPL token on the Solana blockchain, enabling consumer-scale apps to transact swiftly, with minimal-to-no fees. Learn more at Kin.org.