👨🏼‍💻

khriztianmoreno's Blog

Home Tags About |

Posts with tag discuss

The Web Stack You Cannot Ignore in 2026

2025-12-26
web-performanceidentitypwaaidevtoolsprogrammingweb-developmentdiscuss

After going through roadmaps, specs, Chrome Dev Summit talks, and real signals from production, my prediction is simple:Web development in 2026 moves toward more native capabilities, less unnecessary JavaScript, and performance you can measure in the real world.This isn’t a “cool tools” list. These are the areas that become non-optional.1. Performance (Core Web Vitals + Soft Navigation)If you only fix one thing, fix this. Performance is the priority. No debate.Why it will be vital in 2026Google is doubling down on real user experience, not synthetic benchmarks. Soft Navigation also changes how modern SPAs (and “MPA-like” apps) are evaluated.In 2026:If you don’t improve INP and LCP, you don’t just “lose SEO” — you lose conversions.If you don’t measure soft navigations correctly, you’ll ship “faster” routes with fake metrics.What changesCLS stops being “cosmetic”.INP fully replaces the old “FID mindset”.SPA performance gets judged like an MPA.What you should masterweb-vitals in productionLong tasks (and what creates them)Soft navigation heuristicsRUM > LighthouseResourcesWeb VitalsSoft NavigationCrUX2. Identity: Passkeys + FedCMTraditional login is dying. It just doesn’t know it yet.Why it will be vital in 2026Passwords are both a technical and legal liability. Passkeys reduce friction and fraud. FedCM is the browser’s real answer to identity in a world without third‑party cookies.In 2026:A product without passkeys will be perceived as outdated.“Classic OAuth” without FedCM will degrade (or break) flows users care about.What changesPasswordless becomes normal.Browser-native login UI becomes the expectation.Less JS. More platform.What you should masterWebAuthnPasskeys UX patternsFedCM flowsPrivacy-preserving identityResourcesFedCMPasskeysWebAuthn3. Fugu / PWA APIsThe web talks to hardware now. The debate is over — what’s left is execution.Why it will be vital in 2026Web apps compete directly with native when the capability gap is small. Browsers keep shipping standards-based APIs, which means fewer dependencies and less glue code.In 2026:WebUSB, File System Access, and Badging stop being “rare”.PWAs feel more and more like first-class apps when the use case fits.What changesReal offline capabilitiesDeeper OS integrationFaster UX without native wrappersWhat you should masterFile System Access APIBackground SyncBadging APIPWA install heuristicsResourcesWeb capabilitiesProgressive Web Apps4. AI for Web Developers (Built-in AI APIs)AI stops being “just a SaaS”. It becomes part of the browser.Why it will be vital in 2026Lower latency. More privacy (because local is the new default). And better UX without forcing every product to build an expensive AI backend.This is not “embed ChatGPT”. This is native AI, progressively enhanced.In 2026:On-device AI becomes the default when available.AI-driven UX becomes a real differentiator.What changesSmaller, faster models running locallyFewer external callsUI patterns that adapt in contextWhat you should masterOn-device inference constraints (and fallbacks)AI UX patterns (assistive, not intrusive)Privacy-first AIProgressive enhancement with AIResourcesAI in Chrome5. DevTools & Browser AutomationTraditional debugging doesn’t scale.Why it will be vital in 2026Apps get more complex. Performance issues get more subtle. And manual testing simply isn’t viable if you want speed and quality.In 2026:Observability from DevTools becomes a daily habit.Automation becomes part of the workflow, not a “QA phase”.What changesSmarter DevToolsMore integrated testingDebugging centered on real UXWhat you should masterAdvanced Performance panel workflowsLighthouse CIPuppeteer / PlaywrightTracing and deep profilingResourcesChrome DevToolsLighthouseMy final prediction (no marketing)If I had to bet on only one foundation:Performance + Identity will be the base. Everything else sits on top of that.The web in 2026 will be:More nativeFasterMore privateLess dependent on “framework magic”The rest is noise.I hope this has been helpful and/or taught you something new!Profile@khriztianmorenoUntil next time

Predictions 🧞‍♀️💻 2024

2023-12-04
programmingweb-developmentdiscuss

Some points you should pay attention to for this year 2024 that will surely have a high impact on the technological ecosystem.Bun achieves its goal of becoming the default frontend runtime: They still have some hurdles to overcome, but if they manage to provide a drop-in replacement for Node that instantly improves your application's performance 10x, it will be an obvious choice for most developers. The v1.0 release last September was a major step towards overall Windows compatibility and stability, and the bet is that Bun will start becoming the default choice this year.AI will replace no-code/low-code tools: It turns out that AI is much better and faster at creating marketing analytics dashboards. Tools like Basedash and 8base already use AI to create a full set of requirements, custom internal tools, and others will emerge to replace drag-and-drop builders to create sites that don't rely heavily on business logic.Netlify is acquired by GoDaddy: With multiple rounds of layoffs, 2023 was clearly not the best year for Netlify. But sometimes the best way to recover is to find a new ~~sugar daddy~~, GoDaddy. After retiring the Media Temple brand a few months ago, it looks like GoDaddy might be back in the acquisition market for a platform like Netlify.Any other ones you can think of? Help me update this post!!Profile@khriztianmoren

Predictions 🧞‍♀️💻 2022

2022-01-04
programmingweb-developmentdiscuss

Some points you should pay attention to for this year 2022 that will surely have a high impact on the technology ecosystem.RIP Babel and Webpack: They will not disappear forever, but will be largely replaced by new compiler tools that are faster and more intuitive, such as SWC, esbuild and Vite.Serverless will help frontend developers become (real) fullstack developers: and (hopefully) get paid accordingly. Much of the serverless technology is based on V8 and is adopting Web APIs, so frontend developers will already be familiar with the key parts of the serverless infrastructure. Now, instead of starting up an Express server and calling yourself a “fullstack developer”, Serverless will allow you to actually be one.Next.js will become less of a React meta-framework and more of a web meta-framework: Vercel has already hired Rich Harris (aka Lord of the Svelte) and has shared their plans for an edge-first approach to the web with any framework. They will lean even more on this in 2022, adapt to more JS frameworks/libs (with pillowcases full of cash) and prepare for an IPO.No/Low-code tools will dominate even more: We will probably continue to ignore them; meanwhile, more agencies and teenagers will make millions of dollars submitting sites without writing a line of code. In 2022, we'll also start to see more established software companies with “real developers” leveraging no-code or low-code tools because the best code is the code you don't have to maintain.Meta will cede control of React: Just like when they created GraphQL Foundation in 2018, Meta will create a React Foundation later this year and cede control of React. Unlike Microsoft/Amazon/Google, Meta has never (successfully) monetized developers, so React is not a strategic priority for the company. That might be even more true now, with Zuck's eyes on Metaverse and Sebastian Markbåge leaving for Vercel.VC will solve Open Source funding: At least, it will feel that way. With some pre-revenue/traction/pmf OSS projects generating seed rounds at valuations between $25-50MM, you'll want to dust off that old side project of yours. I don't know if it's sustainable (it's not), but it's a lot better than when we relied on Patreon to fund our critical web infrastructure.Netlify to acquire Remix: Bottoms up framework is the wave. Netlify will want the distribution and Remix will want the... money. It would allow the Remix team to spend their time on what they are good at, Remix-the-framework, rather than Remix-the-business. The pairing would give them both a much better chance of catching up with Vercel/Next.js.While all that is going on ...? we can continue to work quietly.Profile@khriztianmoren