Your experience with Next.js App Router and coding assistants?

Discussions
,
1

Hey folks,

I’ve been ramping up my AI skillset lately, both theory and practice. I graduated as an applied math engineer but spent most of my career in web development and a few years with Next.js, so seeing the development of coding assistant is incredibly rewarding, I can finally merge my two passions :slight_smile:

Anyway I’d be eager to get your feedback on using coding assistants to produce Next.js App Router code.

I’ve written a blog post about teaching GitHub Copilot to write proper Next.js route handlers. I’ve started this investigation because the results I got out of the box with Copilot (gpt-4o-mini) were not great at all. Mostly because it fails to catch the newest syntaxes.

What’s your own experience? Do you stick to using a dedicated AI like v0, or do you get better results with other editors/assistants (Cursor, Cline etc.) namely those with contextualization features.

3 Likes
2

Thanks for sharing your thoughts here, Eric!

In my experience, nothing beats v0 when bootstrapping your frontend application. But I’ve used Copilot and Codium as plugins to my code editor in the past and they both were very good at suggesting or autocompleting code snippets for me.

You might find this post interesting;

4 Likes
3

+1 @anshumanb’s comment. v0 is knows it everything about Next.js afterall. :smile:

I also encourage you to catch up with the following content on v0 usecases directly from the community. Might be helpful to get some ideas :wink:

4 Likes
4

In my experience (hopefully Vercel is okay with me saying this :smiley:), v0 is great at Next.js (it probably is prompted with info about the latest version, unlike other AIs) and also great for prototyping.

However, for larger codebases, I almost always use Cline (if I’m using VS Code) or Zed IDE instead of v0 if I’m going to use AI.
Of course, most of the time, I get to a point where AI can’t help me that much anyway and just do it all by hand. :slight_smile:

2 Likes
5

We always welcome the feedback, @BestCodes! Thank you :folded_hands:

1 Like
6

@bestcodes thanks for the feedback ! I’ll definitely give a shot at Cline, I think they figured that Next.js was a big deal for web development and have a specific logic to scrap the documentation and transform it to Markdown. For other technology they will consume a GitHub doc repo. So yeah probably a good solution.

2 Likes
7

I use Cursor for day to day development and v0 for quickstarting new components, iterating on designs, and anything I need to do on mobile

Big fan of just pasting screenshots into v0 and toying with new ideas

2 Likes
8

Also, in case it’s helpful → this is an example of what I built mostly on v0.

1 Like