@nextjs@convex Faster development
Traditional backends require:
controllers
routes
socket handlers
database services
Convex simplifies this into:
queries
mutations
actions
Much less backend boilerplate.
Today I built a real-time multi-thread chat application for learning.
Stack:
• @nextjs
• @convex
The goal was to explore a simpler architecture for real-time AI chat systems.
Here’s why I chose this stack 👇
Integrated payments in a Next.js app today using @dodopayments.
Steps:
• Install package
• Add API keys
• Create checkout route
• Use built-in webhookHandler
Payment flow was ready.
Compared to Razorpay which needs order creation, signature verification, and more setup.
Curious if others have faced this with a self-hosted Supabase setup.
Running everything on a VPS using Coolify.
If you’ve debugged realtime issues like this, I’d love to hear what caused it.
Debugging a WebSocket issue in my self-hosted Supabase setup today.
Everything works in my Next.js app except real time subscriptions.
Error:
"WebSocket is closed before the connection is established."
Here’s what I’m checking 👇
React / Next.js behavior
React Strict Mode mounts components twice in development.
This can quickly create and close WebSocket connections, which may trigger this error.
Testing this hypothesis next.
@dejvdesign Hi @dejvdesign
I'm interested for the Full-Stack role. My experience is deep in Next.js/React, and I specifically built ui component using shadcn.
Ready to hit the ground running on the MVP!
@realsimon So sorry for the delayed response on this. Yes, this is definitely interesting. We are an AI product team and I'd love to chat more about the Alliance cohort. Are you still open for a discussion?