New to Next - start with app router?
Unanswered
Asian black bear posted this in #help-forum
Asian black bearOP
I'm looking for some general advice here. I'm an experienced full stack developer with lots of time on React and Express stacks. I am convinced Next is the future for my projects.
I'm trying to figure out if I should be starting off with the app router or if it's still too new - particularly for someone new to Next. It looks like most supporting projects (i.e. NextAuth) haven't caught up with documentation or support for the app router just yet.
I would rather not build on an approach that's going to be outdated in the very near future, but I feel like I'm in a bit of quicksand trying to get things done the 'new' way.
Do I step back and go with the pages router for now and accept that I'll have to update sooner than I'd like to, or do I grind it out with the app router and expect that it'll get better quickly?
I'm trying to figure out if I should be starting off with the app router or if it's still too new - particularly for someone new to Next. It looks like most supporting projects (i.e. NextAuth) haven't caught up with documentation or support for the app router just yet.
I would rather not build on an approach that's going to be outdated in the very near future, but I feel like I'm in a bit of quicksand trying to get things done the 'new' way.
Do I step back and go with the pages router for now and accept that I'll have to update sooner than I'd like to, or do I grind it out with the app router and expect that it'll get better quickly?
2 Replies
App router is the newest investment from the team, so absolutely go with that if you want as much future-proofing as possible. I don't personally have any issues with developing on the app router. It seems very stable
But I believe you can mix and match both routers if that suits your needs