إنشاء loading.tsx وعناصر Skeleton ذات معنى

In the App Router, a loading.tsx file is special: Next.js automatically wraps your route segment's page.tsx in a React <Suspense> boundary and shows loading.tsx as the fallback while the server component streams.

• You get an instant loading state with zero manual Suspense wiring.
• It only triggers on the server-render of that segment, not on every client interaction.
• The fallback is shown immediately while the page's async data resolves.

This lesson is about making that fallback meaningful so the user perceives speed and the layout does not jump.

Drop a loading.tsx next to your page.tsx in any route segment. Its default export is rendered as the Suspense fallback for that segment and everything below it.

• It is a normal React component — it can be a Server Component (the default) since it renders only static markup.
• No props are passed to it; it must be self-contained.
• Keep it lightweight so it ships and paints fast.

A bad loading state replaces your page with a centered spinner, then snaps to a totally different layout when data arrives. That visual jump hurts perceived performance and Cumulative Layout Shift (CLS).

A good skeleton mirrors the final layout:

• Same number of cards, rows, and columns.
• Same approximate widths and heights as the real content.
• Same spacing and grid structure.

When real data swaps in, nothing moves — only the gray placeholders fill with content.

Start with one tiny building block: a Skeleton box that renders a gray, rounded rectangle. You compose everything else from it.

• Accept className so callers control width, height, and shape.
• Add an animate-pulse style (Tailwind) or a CSS shimmer for the loading feel.
• Mark it aria-hidden — it is decorative, not real content.

Build the skeleton by copying the structure of the real component, then replacing text and images with Skeleton boxes sized to match.

• An avatar becomes a circle: h-10 w-10 rounded-full.
• A title line becomes a wide bar; a subtitle becomes a shorter, thinner bar.
• Use the same container classes (padding, gap, border) as the real card.

For lists and tables, render a fixed count of row skeletons — enough to fill the typical viewport so the page looks complete.

• Reuse the single-row skeleton inside an array.
• Pick a count that roughly matches your usual page size (e.g. 6–8 rows).
• Keep the same gap and wrapper as the real list to preserve spacing.

Now loading.tsx just composes your skeleton components inside the same outer layout as the page. The header that is static (not data-dependent) can be rendered for real even in the loading state.

• Render the real, instant parts (page title, tabs).
• Swap only the data-bound regions for skeletons.
• This gives a page that feels half-loaded already.

loading.tsx covers the whole segment — if any data on the page is slow, the entire fallback shows. Sometimes you want finer control so fast content paints first.

• Use loading.tsx for the segment-wide first paint.
• Wrap individual slow components in <Suspense> with their own skeleton fallback to stream them independently.
• Combine both: a light segment skeleton, plus granular Suspense for the slowest widget.

How many skeleton rows should you show? A small helper keeps it consistent and clamps to a sane range so you never render an absurd number of placeholders.

This logic is plain TypeScript — no framework involved — so you can unit-test it in isolation.

Skeletons are decorative, but they still affect assistive tech and motion-sensitive users.

• Mark the loading region with aria-busy="true" and individual placeholders with aria-hidden="true".
• Provide a visually-hidden status like <span className="sr-only">Loading users</span> for screen readers.
• Respect prefers-reduced-motion so the pulse animation does not run for users who opt out.

Avoid these mistakes that defeat the purpose of a skeleton:

• Spinner-only fallback: gives no layout cue and guarantees a shift when content arrives.
• Mismatched sizes: if the skeleton card is 60px tall but the real card is 96px, the page still jumps.
• Forgetting the wrapper: different padding/grid between skeleton and page shifts everything.
• Skeleton over fast data: if a segment loads in <100ms, the flash of skeleton can feel worse — consider component-level Suspense for only the slow parts.

Test your understanding of route-level loading states and skeletons.

You learned how to craft meaningful loading states in the App Router:

• loading.tsx is an automatic Suspense fallback for its route segment.
• Build skeletons from a small Skeleton primitive and compose them to mirror the final layout.
• Match wrappers, counts, and dimensions to avoid layout shift (CLS).
• Render instant static parts (titles, tabs) for real; skeleton only the data-bound regions.
• Use loading.tsx for segment-wide first paint and component-level <Suspense> to stream slow widgets independently.
• Handle accessibility with aria-busy, aria-hidden, an sr-only status, and prefers-reduced-motion.