bdr888 / ag Goto Github PK

• The original code fetched and rendered the data and components on the client. I chose to move that work to the server to speed up performance and not avoid being subject to the client's network connection and device constraints. Using the server components has these additional performance benefits .

• Additionally, I updated the loadData() function that mutates the primary data to use Promise.all. This will perform both the primary and secondary fetch operations in parallel instead of sequentially, reducing time needed to get and then display all the data together.

• Finally, I reduced the time complexity of the algorithm by first creating a map of the secondary data, then using Array.get to retrieve the corresponding item (the updated content).

• I created a reusable React component to display each item of data. The component takes in the a DataItem as a prop, and renders a styled list item.

• The css in the parent list displays each item in a grid, and responsively handles the sizing and aspect ratio of the images for all viewport widths.

• In a real world situation the data fetching functions should catch any errors, and error states should be handled with error boundaries so the user can continue to use the app without it crashing.

• Similarly a loading state could be provided using React Suspense for any section of the UI that relies on data being fetched/mutated.

• The design documents may not account for all viewport widths and device orientations. There are some gaps in the ranges of viewport widths. I would clarify the intended approach with the design team so that all widths and device orientations are accounted for. For instance, should the images be the same size within a range of viewport widths, or shoud the grow to fill the available space?

This is a Next.js project bootstrapped with create-next-app.

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Inter, a custom Google Font.

To learn more about Next.js, take a look at the following resources:

• Next.js Documentation - learn about Next.js features and API.
• Learn Next.js - an interactive Next.js tutorial.

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.