Auth with Clerk and Convex
I'm very new to Convex and am just going through the tutorials and documentation. But from what I've seen so far it really is the missing piece I've been looking for. Really excited to test this fully on some projects.
However, it still seems like there's a little bit of friction when setting up auth. From reading some of the support threads it seems that, if you're using Clerk, then you should almost certainly have a users table with a Clerk ID so that when a user logs in you can grab the Convex user via the Clerk ID and then base all Convex queries and mutations on the Convex user ID (hope I got that right). While there is a template, and docs for how to implement this it feels perhaps a little too manual when creating a new app.
From a very new users perspective, I think that if Convex were to give a bit of attention to this area and make it super easy to add auth so that you almost didn't even have to think about it that would be amazing and you could effectively just spin up a new app with a db (via Convex) and have auth pretty much just work and you could just start to query users in the Convex table. I think if this was the case it would make Convex even better (it's pretty incredible already!).
In summary, at the moment I can create a Next.js app with Convex really easily, so I have a deployment and db support (yay!). But setting up auth still takes a little effort. I'd love to be able to spin up a Next.js app, add Convex, and auth (Clerk) and just have it all work as quickly as possible, so I can focus on building the app.
Would love to get feedback from developers who have been using Convex with Clerk for some time to know if this problem effectively disappears once you're super familiar with all the API's etc.
However, it still seems like there's a little bit of friction when setting up auth. From reading some of the support threads it seems that, if you're using Clerk, then you should almost certainly have a users table with a Clerk ID so that when a user logs in you can grab the Convex user via the Clerk ID and then base all Convex queries and mutations on the Convex user ID (hope I got that right). While there is a template, and docs for how to implement this it feels perhaps a little too manual when creating a new app.
From a very new users perspective, I think that if Convex were to give a bit of attention to this area and make it super easy to add auth so that you almost didn't even have to think about it that would be amazing and you could effectively just spin up a new app with a db (via Convex) and have auth pretty much just work and you could just start to query users in the Convex table. I think if this was the case it would make Convex even better (it's pretty incredible already!).
In summary, at the moment I can create a Next.js app with Convex really easily, so I have a deployment and db support (yay!). But setting up auth still takes a little effort. I'd love to be able to spin up a Next.js app, add Convex, and auth (Clerk) and just have it all work as quickly as possible, so I can focus on building the app.
Would love to get feedback from developers who have been using Convex with Clerk for some time to know if this problem effectively disappears once you're super familiar with all the API's etc.
