Vue.
Vue 3 is the component layer underneath every Remiam frontend. The studio picked Vue over React years ago for the cohesion of its ecosystem — Nuxt for the meta-framework, Pinia for stores, Nuxt UI for components, Vue Router for routing, Vite under the hood. The composition API and Single-File Components keep the developer experience consistent between a small marketing site and a 10-feature internal tool. Remiam writes a lot of Vue, and writes about it too — the notes catalogue includes the Vue 3 Composition API in-production essay and Nuxt-vs-Next revisited several years apart.
- 4 Jun 2025→
Nuxt vs Next, revisited: seven years later.
We wrote this comparison in 2018. Nuxt and Next have both shipped two major versions, an entire rendering model shift, and a complete rethink of how data fetching works. Time to revisit.
- 14 Mar 2022→
Vue 3 and the Composition API, two years in.
Composition over options. After 24 months in production across half a dozen systems, here is what worked, what hurt, what we would do differently, and the composable patterns we now reach for by default — with real code from real projects.
- 8 Oct 2021→
Why we use Nuxt for almost everything we ship.
Nuxt isn't trendy. It's just the right shape for the systems we tend to build — operational, content-heavy, SSR-first, with realtime in the corner. After 30+ production projects, here is the full case, the patterns we default to, and the brief categories where we still reach for something else.
- 30 Aug 2018→
Nuxt vs Next: the meta-framework decision in 2018.
Two frameworks. Two ecosystems. Same pitch — server-rendered, file-based, batteries included. After shipping production work in both this year, here's the head-to-head we keep coming back to and the decision tree we use on new briefs.