<ul data-eligibleForWebStory="true"><li>Building apps with Next.js involves optimizing server tasks post-response using the after() API of Next.js 15.</li><li>after() allows running logic after route rendering without impacting the client's experience, beneficial for tasks like analytics or logging.</li><li>It works in Server Components, Actions, Route handlers, and Middleware, with varying access to request info.</li><li>Nested after() calls execute in reverse order of their rendering, providing a clean way to handle post-response tasks.</li><li>after() runs even during errors, ensuring critical tasks like logging continue despite route failures.</li><li>Key considerations include after()'s static nature, need for manual gating of conditional logic, and limitations in dynamic reactivity.</li><li>alternatives to after() include waitUntil() for Edge Middleware and await for tasks that must complete pre-response.</li><li>Utilizing after() effectively can significantly enhance web app performance and user experience by deferring non-critical tasks.</li></ul>

How to optimize your Next.js app with after()

Discover more