Vue.js Development for Products That Can't Afford to Be Rebuilt

A Vue.js developer you hire on your own brings one person's experience. A developer from a Vue development agency brings the experience around them too. We're an official Vue Partner with Vue developers across the company, so the ones we place can get a second opinion from colleagues, with a delivery manager assigned to your engagement. The team can also grow or shrink as your roadmap changes, and when the project needs other roles, such as designers, QA engineers, product managers or Laravel developers, they come from the same company instead of separate hires.

When interviewing a Vue.js developer, look for solid Vue 3 fundamentals first: reactivity, the Composition API and single-file components, which the Vue docs recommend for building full applications. Then check the tools your project uses. For state management that's usually Pinia, which the Vue team recommends for new apps; older apps may still run on Vuex, which is now in maintenance mode. If you render on the server, add Nuxt. A useful practical test is to ask candidates to walk through a real component and explain how its reactive state behaves. It's also one of the things our own Vue code reviews check.

Vue Partners are agencies endorsed by the Vue team and listed on vuejs.org. Agencies apply with their Vue track record: how long they've worked with Vue, how many Vue projects they've delivered, and examples of that work. Seven are listed today, including Redberry. For you, that means you can check the expertise on vuejs.org rather than take a Vue.js development agency at its word. At Redberry, it also means Vue is our standard front end, not a side skill.

Yes. It usually starts in one of four ways:

• As a managed project. We take ownership of the product. Discovery begins with an audit of your codebase, then delivery runs the way it does on our own builds: two-week sprints, a tested build for you to approve, and production releases once you sign off.
• As a rescue. Over a third of our engagements start this way, after another team has hit a dead end. We stabilise first, with monitoring, proper environments and tests around the parts that matter most, then move on to new features.
• As a migration. Moving from Vue 2 to Vue 3, or from an older Nuxt version to a current one, can usually happen in stages while the product stays live (see the Vue 2 question below).
• As an extension of your team. Our developers work in your Jira and your release process, and the aim is for them to be contributing code by the end of their first week.

Yes. Our services are modular, so we can take on the Vue or Nuxt front end on its own and build against your API, or add Vue developers to your existing front-end team. Most products we build are API-first with a separate front end, so working to another team's API contract is normal for us.

Vue 2 reached end of life on 31 December 2023 and no longer receives updates or fixes, including security fixes. The Vue team recommends moving to Vue 3. Vue's migration build helps: it runs most Vue 2 code on Vue 3 and warns you about what needs to change, though apps that rely on Vue 2 internals or older component libraries take more work. If you can't migrate straight away, commercial extended support for Vue 2 is available as a stopgap. We start migrations with a codebase audit, so the estimate reflects what's actually there.

It mostly depends on who needs to find the product. Nuxt renders pages on the server, so content appears faster and search engines can index it, which matters for public products like marketplaces and online stores. A single-page app suits tools behind a login, where search visibility doesn't matter. On a Laravel backend, Inertia lets you build Vue pages on Laravel's own routing and controllers instead of a separate API, and it's what Laravel's official Vue starter kit uses. We settle this in discovery, before any code is written.

We think so. It's the front end we've chosen as our default and pair with Laravel in our core stack, and some of the Vue products we work on have been in active development for years. Two things give us confidence. Vue is an independent project that has been financially sustainable through sponsorships since 2016, so its direction doesn't hang on one company's priorities. And when Vue 2 reached end of life, the team gave projects a final release and a migration path instead of leaving them stranded. In our experience, how long a product lasts depends more on how it's built than on the framework it's built with.