Services
Frontend development
for product teams.
I'm a freelance developer in Copenhagen, and since 2015 I've shipped code inside large enterprises and product-led companies. On the frontend, I help teams with architecture, product UI and component libraries - inside your team for the long term, or as a scoped project with a clear brief.
When to bring me in
Frontend problems
I help teams solve.
The frontend has outgrown its structure
New features take longer when every screen solves the same problems in a slightly different way. A clear frontend architecture and a set of shared components give new work a pattern to follow.
Several products should feel like one
When a company runs more than one frontend, a shared component library keeps brand and behaviour in one place. For Nyx, that meant one Vue framework, versioned through npm, underneath their frontend applications.
A design has to reach production intact
I'm a developer, not a designer, but I implement designers' work pixel-perfectly from Figma, Sketch or prototypes. When there's no designer in the picture, I can make the UI decisions myself.
The team needs senior frontend capacity
I've led delivery alongside teams of up to 12 developers, and I've owned outcomes solo when that was what the situation called for. Either way, I work in your tools and your process.
What you get
Frontend work,
from architecture to UI.
Vue and Nuxt are my default, and I also work in React, Next.js and TypeScript codebases. If your team has already chosen a stack, I work within it.
- Frontend architecture and project setup for new products and rewrites
- Component libraries shared across applications and versioned through npm
- SPAs, dashboards and customer-facing product UI
- Staff and back-office tools with dense workflows, such as booking and scheduling
- Design to code from Figma, Sketch or prototypes
- Mobile-first performance work on public-facing sites
Cases
Frontend work
in production.
- Long-term contract
A shared Vue framework and a large back office
I built Nyx's reusable Vue component framework and led the frontend for their largest back-office application. The platform serves more than 250,000 users.
I built Nyx's reusable Vue component framework, with 147 components shared across their frontend applications through npm, and led the frontend of version 2.0 of their largest back-office application.
- Campaign site
DK Hostmaster's 20-year story, for the public and the press.
Static Nuxt front end with year-by-year storytelling and predictable hosting. Content lives in the repo so the team could update and hand it off without a CMS.
A scoped build with a fixed launch date: a statically generated Nuxt timeline for DK Hostmaster, tuned mobile-first so it stayed steady when press coverage sent traffic spikes.
- Marketing site
A marketing site the studio could publish from WordPress, and visitors would feel in the browser.
Scoped project for a design-led agency: mockups translated to a Nuxt front end, with WordPress headless so the team could ship cases and campaigns without learning a new CMS.
Nicolai Qvindbjerg's design translated into a Nuxt front end that stays faithful to the mockups, typography, spacing and motion included.
- Enterprise application
Policy and billing in one staff platform for a Danish insurance mutual.
Long-term contract on Slim PHP services and a Nuxt 2 staff app for memberships, tariffs, invoicing, settlement and reporting, replacing legacy back-office tooling the team could no longer extend safely.
Frontend work on a Nuxt 2 staff application with dozens of operational screens for policy, billing and settlement, alongside work on the PHP services behind it.
"Emil has proven to be very structured in his development process and always pays significant attention to detail in everything from business logic to front end UI, which results in viable and maintainable projects."
Nicolai Cornelis
CEO @ Nyx Systems
How it works
From a first message
to launch and after.
Share the context
Tell me what you're building, who it's for and what timeline you're working toward. Stack preferences, design constraints and links to a repo, Figma file or existing product all help.
Agree on the setup
I work on an hourly rate and I'm transparent about it before we start. For scoped work, you get an honest hour estimate tied to a clearly defined brief, so you know what you're committing to upfront.
Work inside your workflow
I join your Slack, follow your Git workflow, attend your standups and fit into your existing processes, whether the team is a startup or a large enterprise.
Launch and keep going
I don't disappear after deployment. Most of my clients keep me on for maintenance, iterations and new features, and some partnerships have been running for 4-8 years.
FAQ
Hiring a
frontend developer.
No. Vue and Nuxt are my default, and I also work with React, Next.js and TypeScript. When your team has already chosen a stack, I work within it.
Yes, that's one of the most common setups I work in. I join your Slack, follow your Git workflow, attend your standups and fit into your existing processes. I've been embedded in teams from startups to Fortune 500 enterprises.
I'm a developer, not a designer. If you have a designer, I'll implement their work pixel-perfectly. If you don't, I can handle design decisions myself - after 100+ engagements, I've developed a strong eye for UI.
Yes. For Nyx I built a Vue component framework with 147 reusable components, shared across their frontend applications through npm with a strict semantic versioning strategy.
Yes. For smaller teams and focused builds, I often own a project A-Z with a defined scope, and I'll give you an honest hour estimate tied to a clearly defined brief. DK Hostmaster's anniversary timeline is an example of that kind of project.
Related services
Other ways
I can help.
Vue & Nuxt development
Framework-specific work when your product is built on Vue or Nuxt: component frameworks, rendering strategy, headless CMS front ends and migrations.
Full-stack development
When the work reaches beyond the interface into APIs, integrations, hosting and deploy pipelines.
Looking for
the right developer?
Whether you're ready to start or just exploring your options, feel free to reach out. No commitment, no pressure.
I usually respond within 2 hours.