I can t yet figure out how to deal with | Next.js | Page 1

finite dagger Oct 25, 2022, 10:11 PM

#

can you give an example of how they would be different? if they are considerably different, why not have separate pages?

livid notch Oct 25, 2022, 10:15 PM

#

For example if on the desktop we have a layout with a category panel (data get from sever) - and a product list as main content, while on mobile only the product list is needed (categories are in a different page). For mobile we don't wanna fetch all the categories because we don't render it

finite dagger Oct 25, 2022, 10:18 PM

#

are you fetching using multiple fetch() queries (one for categories and one for product list)? or are you using one query to fetch all that? If it's just one query, then the best thing to do would just simple be hiding categories behind a menu or not showing at all on mobile.

livid notch Oct 25, 2022, 10:21 PM

#

Two different queries, for mobile the idea is not to call the get categories api (on server side)

finite dagger Oct 25, 2022, 10:21 PM

#

oh are these queries happening in a server side props function?

livid notch Oct 25, 2022, 10:22 PM

#

Yes, for example using the new experimental "use"

finite dagger Oct 25, 2022, 10:24 PM

#

ok I'm not familiar with the use feature yet but I think it might not be worth optimizing for this unless it becomes a real problem for the mobile users or if you're struggling to load both on mobile (due to speed/bandwidth issues)

livid notch Oct 25, 2022, 10:30 PM

#

The same happens with getServerSideProps, if this call for categories is heavy then mobile users are unnecessarily affected. But maybe the solution is more about improving this api performance

#I can t yet figure out how to deal with