One frustrating feature of RC is the bad user-experience with dev/prod projects and thus the dashboard.
I think Clerk does this very well, allowing a single project with a dev/prod instance (picture 1). This makes things very easy to flip between the two, isolates sandbox data vs real data, and allows very clear separate API keys, management, etc.
Example -
Lets assume I have a very active project, post launch perhaps:
If I wanted to test adding a new type of webhook for the firebase extension, without the risk of blowing up my firebase functions quota, I’d need to set up an entirely separate RC project, duplicate all the settings over (which is equally a painful process right now), update my local application with new API / public keys, just to test the addition of a single webhook event.
I would *LOVE* to see a unified unified approach that really separated the environments, and the intent behind the data. I don’t believe the sandbox toggle is sufficient - here’s a RC example:
The first image (picture 2) shows my sandbox data toggle on, while testing.
The second image (picture 3) is when I turn sandbox data toggle off.
Why would the users I created during sandbox mode, against a sandbox stripe persist on the dashboard?
Would love to chat more! There’s tons of other UX things I think could really enhance the UI/UX as new customers come join RC :)
Thanks, team!
PSA: I found this post from 2+ years ago, seems to be after the same rough experiences -
