why you choosed this strategy of client & server separate apps instead a single nextjs app with api/routes for the server...? arent you sacrificing simplicity? not critic, jsut an honest question?
@@jjpp20072007 I appreciate the honest question! The main reason for choosing separate client and server apps instead of a single Next.js app is flexibility and scalability. By separating them, I can independently scale the client and server as needed, optimize performance for each, and even use different technologies or services tailored to their specific needs. 😃
Great work again @CodeWise. I'm looking forward to what you are going to build next.
Nice, is there gonna be a part 3?
can you make a short video of Google Auth changes when deploying. I tried many things but still it doesn't work
In the Google console do I put the redirection url to the server or to the frontend?
yes sorry i forgot that part. u should replace the localhost one with the actually deployed backend url!
why you choosed this strategy of client & server separate apps instead a single nextjs app with api/routes for the server...? arent you sacrificing simplicity? not critic, jsut an honest question?
@@jjpp20072007 I appreciate the honest question! The main reason for choosing separate client and server apps instead of a single Next.js app is flexibility and scalability. By separating them, I can independently scale the client and server as needed, optimize performance for each, and even use different technologies or services tailored to their specific needs. 😃