# infinite scroll Published articles for infinite scroll. 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 Infinite Scroll Was a Design Crime. Now Meta is Paying for It. DevFeed: [The Infinite Scroll Was a Design Crime. Now Meta is Paying for It.]() Original publisher: [Read original article]() Author: Simon Sterne Published: 2026-08-25T11:30:00Z Content type: opinion Language: en Sources: [Web Designer Depot]() Topics: [web design](), [User experience (UX)](), [Usability](), [Front end](), [Web Development](), [Web](), [Document Object Model (DOM)](), [Software Engineering](), [browser](), [browsers](), [CSS]() Tags: [addictive-design](), [behavioral-design](), [browser](), [browsers](), [css](), [dark-patterns](), [design](), [design-ethics](), [digital-detox](), [digital-wellness](), [dopamine-loops](), [ethical-design](), [front-end-development](), [infinite-scroll](), [meta](), [meta-lawsuit](), [meta-trial](), [social-media-lawsuit](), [software](), [tech](), [tech-ethics](), [tech-industry](), [tech-news](), [ui-ux](), [usability](), [user-experience](), [ux](), [ux-design](), [ux-usability](), [web-design](), [web-development]() ### AI overview The article argues that infinite scroll prioritized addictive engagement and advertising over usability, accessibility of stopping cues, and front-end integrity. It discusses legal scrutiny of Meta's Instagram and Facebook feeds, performance and state-management problems, and calls on web professionals to abandon the pattern. ### Source excerpt The infinite scroll was never a UX feature--it was a slot machine disguised as code. Now, as Meta faces a historic trial over algorithmic addiction, web designers must finally confront the ugly truth: we sacrificed basic usability and human willpower just to keep users trapped in a bottomless pit. ## Issue no.14: Software is culture DevFeed: [Issue no.14: Software is culture]() Original publisher: [Read original article]() Author: Figma Published: 2026-01-07T15:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Software](), [Artificial Intelligence](), [Figma]() Tags: [ai](), [culture](), [figma](), [infinite-scroll](), [interfaces](), [software]() ### AI overview Figma's Issue no.14 explores how software shapes culture and everyday life. It discusses the cultural impact of familiar interface interactions, how algorithms influence language and relationships, the evolution of video game interfaces, building an app with Figma Make, and using structured prompts to work with AI in design. ### Source excerpt From ordering delivery in a pinch, to finding genuine connection and meaning, software touches nearly every part of our lives. ## Supabase Beta March 2023 DevFeed: [Supabase Beta March 2023]() Original publisher: [Read original article]() Author: Ant Wilson Published: 2023-04-08T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Artificial Intelligence](), [Next.js](), [OpenAI](), [Databases](), [Deno](), [Framer Motion](), [API](), [LangChain](), [MDX](), [Nuxt.js]() Tags: [ai](), [announcement](), [auth](), [devrel](), [embeddings](), [framer](), [github](), [hackathon](), [hybrid-search](), [infinite-scroll](), [langchain](), [launch](), [next-js](), [nuxt](), [open-source](), [openai](), [postgres](), [vercel]() ### AI overview Supabase's March 2023 beta update previews Launch Week 7, announces a Web3 AI hackathon, and releases a Next.js OpenAI documentation-search template using Vercel, GPT-3, Postgres with pgvector, and Deno Edge Functions. It also highlights an AI-powered ticket system, community projects, and upcoming events. ### Source excerpt We are in full shipping mode 🛥... Launch Week 7 can't come quickly enough! ## Infinite scroll with Next.js, Framer Motion, and Supabase DevFeed: [Infinite scroll with Next.js, Framer Motion, and Supabase]() Original publisher: [Read original article]() Author: Francesco Sansalvadore Published: 2023-04-04T07:00:00Z Content type: tutorial Language: en Sources: [Supabase Blog]() Topics: [infinite scroll](), [Next.js](), [Supabase](), [Framer Motion](), [web design](), [Server-side rendering](), [Caching]() Tags: [cache](), [code-splitting](), [data](), [how-to](), [infinite-scroll](), [next-js](), [performance](), [server-side-rendering](), [user-experience](), [web-design]() ### AI overview A tutorial on implementing infinite scrolling with Next.js, Supabase, and Framer Motion. It explains lazy loading ticket data in batches as the user scrolls, with techniques such as server-side rendering, code splitting, caching, prefetching, and debouncing to improve performance and user experience. ### Source excerpt Lazy load and paginate data on scroll with Next.js and a sprinkle of Framer Motion magic ✨ ## Autosizing, Add All & iOS Redirects DevFeed: [Autosizing, Add All & iOS Redirects]() Original publisher: [Read original article]() Author: Shai Almog Published: 2017-02-07T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [iOS](), [Font](), [networking](), [GUI](), [HTTP](), [Pull Request](), [infinite scroll]() Tags: [fonts](), [gui](), [http](), [infinite-scroll](), [ios](), [networking](), [pull-request]() ### AI overview This Codename One update discusses automatic text autosizing to fit available space, the new Add All shortcut, and changes to iOS HTTP redirect handling. It cautions that autosizing can be expensive and should be used sparingly, especially outside suitable components. ### Source excerpt One of the common requests we received over the years is a way to let text "fit" into the allocated space so the font will match almost exactly the width available. In some designs this is very important but it's also very tricky. Measuring the width of a String is a surprisingly expensive operation on some OS's. Unfortunately, there is no other way other than trial & error to find the "best size". ## Advanced Performance Audits with DevTools DevFeed: [Advanced Performance Audits with DevTools]() Original publisher: [Read original article]() Author: Paul Irish Published: 2015-03-27T15:46:00Z Content type: article Language: en Sources: [Paul Irish]() Topics: [developer tooling](), [Chrome](), [browser](), [Front end](), [Latency](), [infinite scroll](), [Google]() Tags: [audits](), [case-study](), [chrome](), [frontend](), [google](), [infinite-scroll](), [latency](), [performance](), [profiling](), [tooling]() ### AI overview An advanced performance audit of real-world mobile and desktop websites using profiling and the 1000/100/6 performance model. It examines scrolling on CNET, CNET input latency, responsive challenges on Time.com, and infinite scroll on Google Play, with findings intended to improve developer practices, browser APIs, Chrome DevTools, and the Blink rendering engine. ### Source excerpt Recently, I've spent some time recently profiling real-world mobile websites. Using the 1000/100/6 performance model1, and spelunking deep into each app, the findings have been fascinating. I've written up case study documents for each, incorporating all the findings: Illustrated diagnoses for the poor performance What actions the developer should take How Chrome's tooling should improve Questions and insights for the rendering engine (Blink) ➜ Perf Audits: CNet, Time, Google Play In this doc, we look at the scrolling of CNET, input latency on CNET, some very interesting challenges on the responsive Time.com, and infinite scroll on Google Play's desktop site. The intended audience is browser engineers and performance-minded frontend developers. It's fairly advanced, but I'm spelunking deep to identify how the sites butt heads with the browser APIs and architecture. Lastly, we're using this research to improve Chrome DevTools and what you hear from Chrome. Wikipedia eng team scrutinizing their performance millisecond by millisecond. (Yes, it's a long paper printout of the Chrome DevTools timeline flamechart :) Photo by Ori Livneh, CC BY 4.0 (BTW, use this link to view the same doc but with comments enabled) 1 - More on this performance model later. Stay tuned.