In my recent post, “Top 9 Developer Portal Mistakes”, I provided nine critical areas that help you inspect your existing developer community with the hopes of initiating change. One of the areas that I touched on was Manual Submissions & Workflows. The reason that this type of setup is not best practice is because with manual submissions and workflows, you are simply creating more work for your internal team, slowing down the approval process for developers.
One of our clients, Avaya, had this problem when they came to us for help. Though at the time Avaya was delivering something on all areas critical to a successful developer program, the depth usability, and completeness of some of the areas fell short. This was because:
Due to the limitations of the in-house infrastructure, there was no way to scale the program in the way that was desired. So, Avaya brought our team into the mix to help them adopt a more robust technology platform that would deliver a modern and improved user experience. In just a short period of time, Avaya, leveraging dpEngine, relaunched their developer portal, DevConnect.
You might have similar goals, or different ones; however, if they are in the realm of the API Ecosystem, I would encourage you to check out this case study to learn more about how developerprogram.com can help you achieve your developer + partner program goals in 2018.