Next.js Reviews

1. Kurslog team

   · Working at Kurslog · 5 months ago

   Next.js has become the de-facto standard for our frontend engineering team when building modern web applications. The Server-Side Rendering (SSR) and Static Site Generation (SSG) are absolutely essential for our product's SEO strategy and fast indexing.

   The transition to the App Router initially required a paradigm shift for our developers, but it ultimately made our architecture much more scalable. We love that the framework handles the heavy lifting—image optimization, code splitting, and routing—allowing our team to focus purely on business logic. It provides a phenomenal Developer Experience that keeps our deployment cycles fast and predictable.

   Competitors: Remix, Nuxt.js, Svelte, Vite

   Pros:    Out-of-the-box ssr and ssg for excellent seo|Superb developer experience with zero-config setup|Built-in optimizations for images, fonts, and scripts|Highly scalable routing via the app router

   Cons:    The app router requires a paradigm shift and learning curve for the team at first|Caching strategies can be tricky to master and debug across a large, dynamic app

Progressier Reviews

Next.js mentions (1145)

• Building a Multilingual Shop with Next.js

  In this article, we’ll look at how to approach these problems in a Next.js application using the App Router. Rather than focusing on the basics of translating strings, we’ll focus on the technical decisions behind the implementation: how the language is detected, how it’s propagated through the application, how translations are loaded on the server and client, and how localized routes are handled. - Source: dev.to / 7 days ago

• What Browserslist Actually Does in Next.js

  We set up three near-identical Next.js 16 projects to answer a simple question: if you set a browserslist target in package.json, does the build change to match it? We tested three targets (ie 11, chrome 116, about 3 years old, and chrome 139, about 1 year old) and compared the compiled output byte by byte. - Source: dev.to / 4 days ago

• We’re all full stack now

  Blurring of the lines. React Server Components (RSC) and associated frameworks such as NextJS involve code executing on both server and client, while HTMX focuses on markup and emphasises use of full-stack/backend templating engines to generate code targetting the browser. Working with these new tools blurs the distinction between the front end and back end skill set. - Source: dev.to / 16 days ago

• The Past Keeps Changing

  What replaced the laptop, before we get to the schema: Health Auto Export now posts straight to a Vercel function on a daily schedule, a scheduled job pulls lifting history from Liftosaur, and both land in TimescaleDB on Tiger Cloud. No files, no iCloud, no Mac. A Next.js app reads it and tells me whether I hit protein, which is a separate post. - Source: dev.to / 17 days ago

• Getting Started with Shadcn Checkbox in React & Next.js

  This guide shows you how to install and use the Shadcn Checkbox component in React and Next.js. - Source: dev.to / about 2 months ago

Progressier mentions (14)

• Don't upload your PWA to the app stores

  I built Progressier to provide developers with the best possible browser-based PWA installation experience. And I can say, it's nearly as good as Google/Apple's app store installation experience. - Source: dev.to / over 2 years ago

• How to fix iOS push subscriptions getting terminated after 3 notifications

  That's it for me! Hopefully, now you know how to get around push subscriptions being canceled after 3 push notifications. If you have any questions, feel free to contact me here. - Source: dev.to / about 3 years ago

• Web push notifications coming to iOS this year

  When I made Progressier compatible with the desktop Safari update from last October, I had to rewrite a thing or two to put the request for permission inside a click event listener. Doesn't work otherwise. I'd be willing to bet mobile Safari will have the same requirement. Source: over 3 years ago

• Show HN: I made an indie app store alternative with a twist

  The twist is that although it does (part of) the job of an app store, it's not (nor aims to be) an app store. It's a script you add to your existing web app that makes it "self-distributing". Check it out: https://progressier.com. Under the hood, it leverages the concept of "PWA", but it goes further: 1. It creates an installation page for your app that looks like an app store listing. Demo example:... - Source: Hacker News / about 4 years ago

• Does calling the image URL cost anything?

  With something like Progressier, you can set up a caching strategy that essentially says "cache all images located on firebase.whatever-the-url-is.com and never request it from the network after that". It would take approximately 2 minutes to set up -- no code required. Source: over 4 years ago