Category
After the 2023-2024 hype cycle led by Apple Vision Pro, the 2025 valley of disillusionment, and the quiet but real consolidation of Meta Quest 3S and the WebXR stack, it is time to assess honestly where extended reality stands. What works, what has died, what is still alive.
After two years watching every product invent its own interface for talking to an agent, by January 2026 a stable design consensus is emerging about which patterns work, which do not, and what the average user already expects. Time to write down what has settled.
La obligación del EAA entró en vigor el 28 de junio de 2025. Seis meses después tenemos ya primeros expedientes sancionadores, criterios de enforcement y lecciones operativas para equipos que aún corren detrás del calendario. Lo que sí se audita y lo que todavía no.
Accessibility overlays were sold as a magic fix for WCAG and the European EAA directive in one step. In 2025 lawsuits against them have grown and disabled users are speaking out more critically than ever. A look at why they fail and what to do instead.
Qwik has spent two years promising apps that start instantly because, instead of hydrating, they resume execution serialized on the server. With the 1.x series settled and real cases published, this guide checks whether resumability is worth the learning curve and which products benefit most from that client-side JavaScript saving.
HTMX has carved out a niche in small and mid-sized web applications with a clear proposal: less JavaScript, more server. With version 2.0 stable for a year now, it is time to review which enterprise applications benefit and which still need a classic client-side framework.
A year after chat stopped being the only acceptable way to talk to an agent, UI patterns built specifically for agent tasks are emerging. I go through the ones starting to stick and the ones that are just cycle fashion.
The AI features Figma has rolled out since Config 2024 are changing how product design teams work. A look at what each feature delivers, what remains human work, and which habits are taking hold across teams.
Figma Dev Mode is the developer-facing view inside a Figma file: it generates ready CSS, exposes exact measurements, maps variables to tokens, and, with Code Connect, links each component to the real codebase snippet. It solves most of the design-to-code handoff friction, but it does not replace human judgment on accessibility, performance, or responsive behavior.
Almost two years after 1.0, SvelteKit works in production: 30-50% lighter bundles than React, file-based routing, and no-lock-in deployment. It wins for small teams with stack freedom; it loses to Next.js when a team has heavy existing React investment or needs to hire fast.
HTMX returns HTML instead of JSON and makes the server the source of truth for the interface. Where it fits, where it does not, and why version 2.0 leaves it ready for serious projects.
App Router went stable in Next.js 13.4 (May 2023), bringing Server Components, layered caching, and Server Actions, but it demands rethinking the application's mental model. Migrating from Pages Router pays off for new projects and read-only routes; for large applications, the realistic path is incremental, route by route, over several months.
A practical guide for development teams who need to meet WCAG 2.1 without turning accessibility into an endless project. Three layers, a set of proven tools, and 2-3 months of disciplined work are enough for most teams.
