Dude... this is an amazing tutorial! I just sat through the 45 minutes to get an understanding of where you were going and I'm super impressed. I'm now going to crack into VS with a little more confidence. Great job.
@@leonvanzyl Another supplemental video might be saving the responses to a database. I'm certain this is only a few more lines of code but going through the exercise would be extremely interesting.
Great tutorial man. Would be awesome if you can do a part 2, integrating it with whisper and some speaking Api like the one from eleven labs, so the user can talk like with a real assistant!
The new 'next.js' version gave me an initial error message on the bottom left of the screen to upgrade. When I did that, nothing worked so I started over and hid the error message during debugging. Upon deploying to vercel, I do not see a public-facing error message so everything worked. THANK YOU!
Next 13 makes it possible to call API's directly in Server Rendered Components, but this is not what we're using in this video Because we require state management in this tutorial (ie. useState) we need to call API endpoints. Calling API endpoints in Next 13 is still a valid design pattern.
@@leonvanzyl hi Leon. If there is a chance I could have a call with you. Im located in South Africa. And need some help please willing to exchange Rands for your time
Dude... this is an amazing tutorial! I just sat through the 45 minutes to get an understanding of where you were going and I'm super impressed. I'm now going to crack into VS with a little more confidence. Great job.
Thank you for the amazing feedback!
@@leonvanzyl Another supplemental video might be saving the responses to a database. I'm certain this is only a few more lines of code but going through the exercise would be extremely interesting.
Great tutorial man. Would be awesome if you can do a part 2, integrating it with whisper and some speaking Api like the one from eleven labs, so the user can talk like with a real assistant!
Thanks for the idea!
It seems that the new next.js release requires the api key to be posted and called differently 😤😤 Do you concur?
The new 'next.js' version gave me an initial error message on the bottom left of the screen to upgrade. When I did that, nothing worked so I started over and hid the error message during debugging. Upon deploying to vercel, I do not see a public-facing error message so everything worked. THANK YOU!
Next 13 makes it possible to call API's directly in Server Rendered Components, but this is not what we're using in this video
Because we require state management in this tutorial (ie. useState) we need to call API endpoints.
Calling API endpoints in Next 13 is still a valid design pattern.
@@leonvanzyl hi Leon.
If there is a chance I could have a call with you. Im located in South Africa. And need some help please willing to exchange Rands for your time
I was never prompted about the experimental app directory? Any idea why?
At the time of recording, the app directory was still experimental. Now it's standard 😅 .