Shoutout to cloud users - please help us improve our onboarding experience
Hey there π
I'm Elina, product manager here at Zitadel :zitadel: I'd love to understand how was your first time experience of using Zitadel in cloud - was it easy to integrate Zitadel and get your first user created/ logged in or did you struggle somewhere along the way? π€
I'll post a couple of polls and would also appreciate any additional context you can provide about specific areas we should improve. Thank you in advance for your feedback , we'll take it on board and see what we can do:gigilove:
6 Replies
I voted API documentation was confusing over the v1 vs v2, deprecation notices, and the api documentation not showing the minimum version a handler/endpoint was available in so I couldn't even tally it against the version zitadel cloud showed me as running. This is especially pertinent if you're being brave and using the v2beta APIs like I have to.
Thanks @Daniel noted, we know the docs are not easy to navigate right now and are working to have versioned documentation that would be more clear π
I see a few people are voting they can't find info about specific features, would be helpful if you can share what specifically you were looking for? π
As an addition to the comments about the API documentation being confusing, I would LOVE to see more work being done to make Zitadel errors much more clear. For example, I often see errors like
auth-xd4fc8 Invalid Token and I have to literally look into the depths of the Zitadel codebase to understand that auth-xd4fc8 actually means that the Zitadel audience scope parameter is wrong. The auth-xd4fc8 error code was made up in this Discord example but it demonstrates the point.
I find it frustratingly hard to debug Zitadel API flows when the only place that a specific error code is documented is in the code itself, and sometimes even when I can see the code, it's not straightforward to understand the actual reason why the error was returned.
Can there be a list of all error codes and what they actually mean documented somewhere please?As a tiny company CTO we'll like a tinyest subscription as we don't like that we shall pay the same amount than a company that have 25000 users espacially when you need an european server it cost a lot when your just starting
I mean conversely a high availability multi replica service to self host isnβt far off 100 USD a month either. That doesnβt even include your time to maintain and fix anything.
The price is more than fair.