CODEWITHSUNDEEP
javascriptreactjsnext.js
Fabian Lurz
Fabian Lurz

Reputation: 123

Next.js favorite list best practice

I have a next.js application with redux and a node.js Rest-API. You can view items and as often you can store favorites.

Now the view component of the items and the favorites is obviously the same.

I have now two options how I can do it and I want to ask you what is best practice with next.js:

1.Option: Have two routes. One called "search" and one called "favorites".

Pros:

Cons:

2.Option: One route called "search" with a prop for the section

Cons:

Pro:

Redux store is organized the following:

{
  search:{
     results:[],
     total:0,
  },
  favorites:{
     results:[],
     total:0,
  }
}

Upvotes: 0

Views: 1517

Answers (1)

Robert Moore
Robert Moore

Reputation: 2572

It's hard to provide a concrete answer to this question. Do you want one page for users to browse items, allowing them to filter by which ones they've favorited, or do you want one page for searching items regardless of which ones they have favorited and a separate page for finding favorites? This doesn't seem like a best practices problem, it's totally your choice. That said, I would probably prefer option 1 because that is how most applications do it. The fact that it is slow is weird—next.js tends to be very good about preloading. Give your page(s) a try in production mode—often Next.js is just slow to build them in development mode and the real page your users will face will be much faster.

Upvotes: 1

Related Questions