Hi everyone!
We are gathering insights from developers who use (or evaluate) Okta SDKs, APIs, and the Sign-In Widget. We’ve compiled a quick ~5-minute Developer Experience Survey and would love your perspective.
Why take it?
-
Directly influences upcoming SDK features, sample code, and docs.
-
Surface real-world pain points so we can fix them faster.
-
Optional: Please opt in at the end if you can chat in a short follow-up interview. There will be no sales pitches; it will just be pure user research chat.
Start the survey: https://greatquestion.co/oktainc/2o0q6lk9/apply
Questions? Drop a reply below. Thanks for helping us build a better developer experience!
2 Likes
Maybe I was too late, but the “5-min developer experience” survey only asked my role and if I wanted more surveys.
My “developer experience” feedback would be: What’s going on with “Okta Ideas”? When we ask support a question about something that isn’t working, and support has no answers or functionality is missing, they tell us to post on “Okta Ideas”. But Okta doesn’t seem to care about that forum.
More specifically, what’s going on with requests like this:
https://ideas.okta.com/app/#/case/125986
This major gap in the Okta API was requested to be remedied 5 years ago. It’s supposedly been on the “roadmap” for 3 years. From the (admittedly limited) 3 posts I’m watching on the ideas forum that seem like obvious things to fix, Okta hasn’t proactively responded to any of them.
From the outside, Okta doesn’t seem to care about the very feedback they solicit.
