# time-to-interactive Published articles for time-to-interactive. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The Most Expensive Milliseconds Are Unmeasured DevFeed: [The Most Expensive Milliseconds Are Unmeasured]() Original publisher: [Read original article]() Author: Divya Gupta Arora Published: 2026-06-03T17:11:58Z Content type: article Language: en Sources: [Expedia]() Topics: [Mobile](), [render](), [ui]() Tags: [case-study](), [devops](), [engineering](), [login](), [mobile](), [mobile-apps](), [mobile-performance](), [observability](), [performance](), [release](), [software-engineering](), [technology-investments](), [time-to-interactive](), [ui](), [visibility]() ### AI overview This Expedia Group engineering case study describes extending Native Time to Interactive across mobile login screens. The metric was used to evaluate technology investments, compare platform behavior, and detect performance regressions that existing system-health signals did not reveal. ### Source excerpt Expedia Group Technology -- EngineeringHow a screen-level performance metric reshaped platform decisions, engineering ownership, and release disciplinePhoto by Pietro De Grandi on Unsplash For the last few years, my responsibility has been straightforward to state but hard to execute -- owning the traveler login experience across mobile platforms. Not just whether a feature works, but whether it feels responsive, predictable, and trustworthy in the moments that matter most. During login, those moments are unforgiving: if a login screen hesitates travelers don't interpret it as 'a slow render', they interpret it as risk. And when the majority of travelers interact through our mobile apps, performance stops being a technical concern and becomes a product promise. This post is a case study of how, within Expedia Group™'s login domain, we extended Native Time to Interactive (NTTI) across login screens -- moving performance from a late-stage check to a first-class signal we can use to validate technology investments, compare platform behavior, and prevent silent regressions as we ship. The Problem: Mobile reliability rarely fails loudly Mobile performance rarely breaks with a crash. It usually degrades quietly, a button takes a beat longer to respond a screen looks ready, but taps don't register the UI stutters just enough to feel "off" Those are the expensive milliseconds -- because they erode trust without triggering obvious alarms. In our login flows, we were shipping consistently, evolving a major part of our stack, and supporting increasing product complexity. Yet we didn't have a consistent way to answer the user's real question -- "When can I actually use this screen?" Why our existing signals failed We were not blind. We tracked many useful things, crashes and ANRs backend latency and service SLIs some component-level timing signals limited Time to Interactive tracking on onboarding and initial login But we had a gap -- we had visibility into system health, not screen ## Bringing Lighthouse to the App: Building Performance Metrics for React Native DevFeed: [Bringing Lighthouse to the App: Building Performance Metrics for React Native]() Original publisher: [Read original article]() Author: Ben Cripps Published: 2026-03-03T19:13:53Z Content type: article Language: en Sources: [Indeed]() Topics: [React Native](), [Mobile](), [benchmarking](), [Core Web Vitals](), [Google]() Tags: [app-performance](), [core-web-vitals](), [google](), [metrics](), [mobile](), [performance](), [react-native](), [time-to-interactive](), [unsorted]() ### AI overview Indeed describes an open-source React Native repository for measuring Lighthouse-style performance metrics in mobile apps. The article explains adapting Core Web Vitals concepts to React Native, including Time to First Frame and Time to Interactive, to assess screen loading and interaction readiness. ### Source excerpt At Indeed we've open sourced a new React Native repository which makes it simple to measure Lighthouse scores in your mobile apps. We think it will help other organizations better measure their app performance, especially for companies similar to Indeed who are transitioning from a web-first to an app-first approach. You can check out the [...] ## Fullstack GraphQL tutorial: @defer and Apollo GraphOS DevFeed: [Fullstack GraphQL tutorial: @defer and Apollo GraphOS]() Original publisher: [Read original article]() Author: Michael Watson Published: 2022-11-10T11:46:40Z Content type: tutorial Language: en Sources: [Apollo Blog]() Topics: [GraphOS](), [GraphQL](), [Tutorial](), [API](), [Development]() Tags: [apollo](), [apollo-federation](), [caching](), [defer](), [graphos](), [graphql](), [latency](), [time-to-interactive](), [tutorial](), [user-experience]() ### AI overview This tutorial explains how to use GraphQL's @defer directive with Apollo GraphOS to deliver slow parts of a query asynchronously and improve client time-to-interactive. It covers connecting a GraphQL API to a GraphOS supergraph and defining entities with Apollo Federation. ### Source excerpt With Apollo GraphOS, you can improve your client app's time-to-interactive (TTI) and reduce latency in a few lines of code. Just plug your GraphQL API into the supergraph and add the directive to the slow parts of your GraphQL query. When you mark slow fields with , the supergraph knows it can deliver those parts of the result asynchronously. The directive is a proposal to the GraphQL specification that has been in development since July 2020. ## Angular Performance: Route Level Code Splitting DevFeed: [Angular Performance: Route Level Code Splitting]() Original publisher: [Read original article]() Published: 2019-08-26T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Angular](), [Code](), [Development](), [Web]() Tags: [angular](), [cli](), [code](), [code-splitting](), [generate](), [implement](), [lazy-loading](), [load](), [metric](), [performance](), [route](), [time-to-interactive](), [videos]() ### AI overview This tutorial explains route-level code splitting and lazy loading in Angular. It connects loading only the minimum necessary application code to improving time to interactive, and mentions generating lazy routes with the Angular CLI. ### Source excerpt Lorem ipsum dolor sit amet ## Why Web Developers Need to Care about Interactivity DevFeed: [Why Web Developers Need to Care about Interactivity]() Original publisher: [Read original article]() Published: 2017-12-19T17:25:23Z Content type: article Language: en Sources: [Philip Walton]() Topics: [interactive website](), [Web Development](), [JavaScript](), [Document Object Model (DOM)](), [browser]() Tags: [browser](), [javascript](), [main-thread](), [technical](), [time-to-interactive](), [web-developers]() ### AI overview The article explains web interactivity as a page's ability to respond quickly to user input. It identifies delayed JavaScript loading and a busy browser main thread as the two primary causes of poor responsiveness, while focusing mainly on main-thread work. ### Source excerpt Anyone who's browsed the web on their phone has, at one point or another, experienced this situation: You open a web page and click on something, but nothing happens. You click on it again--still nothing.