NPNiharika Pujari

1. Article · Sep 10, 2026 · Niharika Pujari

   Your frontend observability has an accessibility blind spot (opens the original)

   Excerpt · Critical tone · English

   Read excerpt

   Frontend teams have become pretty good at monitoring what happens after an application reaches production. We track JavaScript errors, API failures, latency and Core Web Vitals. When something changes after a release, these signals help us determine whether the application is healthy. But there is one gap I think frontend teams often overlook. An application can look completely healthy in those dashboards while an important workflow is unusable for someone navigating with a keyboard or assistive

   Feedback

2. Article · Jul 31, 2026 · Niharika Pujari

   Why observability matters to frontend teams more than they think (opens the original)

   Excerpt · English

   Read excerpt

   For a long time, I thought of observability as something mainly owned by backend, platform or site reliability teams. Frontend engineers built the interface, handled browser behavior and called APIs. When something failed deeper in the system, another team looked at server logs and infrastructure dashboards. That division works until the application is technically available, but the user experience is not. A page may load while its most important data arrives several seconds late. A request may

   Feedback

Last 90 days. Choose a month to open its work.

Named in the text we hold. One piece can cover several.

Not enough subject data for this period yet.