Data-heavy UIs
Tables, filters, permissions, live status. Sprawling jQuery or a legacy frontend nobody likes.
Frontend - Vue
Vue interfaces that stay clear.
Dashboards, portals and SPAs - components a team can keep building on. Not a frontend that nobody touches after 18 months.
SPA
Dashboards
Design system
APIs
Where Vue fits
Products with dense interfaces - not every brochure site needs an SPA.
Portal next to an API
The Symfony or Laravel backend is in place. The interface is not.
Design without a system
Every page a one-off. We bring in tokens and components.
Performance & A11y
Heavy bundles, no keyboard support. Both are deliverables.
What we deliver in Vue
From the first route to a Storybook-style structure.
SPAs & portals
Vue 3, Router, clear stores. Only as much state as the flow needs.
Dashboards
Lists, charts, bulk actions - with empty and error states.
Design systems
A small component library instead of copy-paste.
Integration
BFF or direct API. Auth, uploads, optimistic UI where it helps.
Approach: the interface as a product
Vue is the glue, not the star. We cut along user jobs: one task, one flow, measurable.
- Clarify the key jobs and permissions
- Lock down API contracts with the backend
- Components and states (empty, loading, error)
- Handover: build, tokens, short docs
How we build frontends
Visible, iterative, no pixel polishing without data.
Flows
Three core tasks, not 40 screens at once.
Structure
Components plus a dummy API, then real data.
Hardening
A11y, performance, permissions, empty lists.
Handover
Build pipeline, tokens, optional maintenance.
What product teams rely on
A frontend that does not embarrass the backend.
No framework by reflex
Sometimes Twig or Blade is enough. We say so.
Integration taken seriously
We do not build against an imaginary API.
Ready to be extended
Your people should be able to commit on their own after two weeks.
Frequently asked questions
Frontend questions without trend promises.
Vue or Angular?
Small to mid-size product UIs: often Vue. Large enterprise frontends with a fixed team split: Angular. We choose by team, not by social media trends.
Nuxt?
When SEO and app come together. Otherwise a Vite SPA behind auth.
Do you take over Vue 2 code?
Yes - we plan the migration to 3 as work, not as a big-bang day.
Who does the design?
We implement and refine it. We do not invent a greenfield brand identity without a brief.
SSR, i18n, tests?
Where the case calls for it. Tests on the expensive flows, not for the sake of coverage.
How do we start?
One flow in staging. Fixed scope after kickoff.
More stacks
Related technologies we often use alongside.
An interface that holds?
Tell us the API and the most important user job - we will sketch the first slice.