As an experienced frontend developer, I technically implement design concepts and ensure an intuitive, error-free user experience. With Vue.js, Nuxt 3 and modern web technologies, high-performance, responsive websites are created that convince on all devices.
Do you need a frontend developer for your agency? Or are you looking for someone to technically implement your website? I'm Jan, I've been working on the web for over 15 years and I turn designs into fast, modern websites.
As a frontend developer, I am the interface between design and technology. I take the drafts of your designers and program them into functioning websites. With Vue.js, Nuxt 3 and a clear focus on performance, solutions are created that not only look good, but are also technically convincing.
What is frontend development really?
Imagine your website as a house. You see the colors of the walls, the furniture and its arrangement, the room layout. That's exactly what I do as a frontend developer – I technically implement all these visible elements.
In concrete terms, this means: I program layouts, buttons, forms, animations and everything that a user sees on your website and with which he interacts. A designer designs how something should look. I make sure that it really works that way.
In my daily work, I translate Photoshop files, Figma designs or Sketch drafts into HTML, CSS and JavaScript. I make sure that the website looks good on every device – from a large desktop monitor to a smartphone.
My way of working and technology stack
I mainly work with Vue.js and Nuxt 3. Why? Because these technologies allow me to build fast and modern websites that remain performant even with complex requirements.
Vue.js is a JavaScript-Framework, that is particularly suitable for interactive user interfaces. Nuxt 3 builds on this and offers additional features such as server-side rendering, which makes your website faster and better optimized for search engines.
The advantage for you: you get a website that loads at lightning speed, works on all devices and is technically up to date. At the same time, the code remains maintainable and expandable – in case you need new features later.
Frontend vs. Backend – the difference explained understandably
"Do you only do frontend or also backend?" I hear this question often. The short answer: I can do both. But let me explain what that actually means.
Frontend is everything you see on a website and with which you interact. The buttons you click, the forms you fill out, the animations that run – that's my main area of work. Backend, on the other hand, is the technology in the background. For example, when you submit a contact form, the backend ensures that your message lands in my inbox.
A practical example: Imagine a website like a restaurant. The frontend is the guest room – the furnishings, the menu, the atmosphere. The backend is the kitchen – this is where the orders are processed and the dishes are prepared. As a full-stack developer, I am familiar with both areas.
For you as an SME, this has a decisive advantage: you don't need two different developers for your project. I can program both the visible interface and the necessary logic behind it. This saves time, money and, above all, coordination effort. If something doesn't work, you know exactly who to call – me.
What makes a good website technically
Let's be honest: we live in a time where a second of loading time can decide over 30 sales per 1000 visitors. Sounds exaggerated? But it's not. The numbers speak for themselves.
The average website loads in 3.21 seconds. The problem: According to a study by Portent, the conversion rate for a loading time of one second is 3.05%. At five seconds, it's only 1.08%. In concrete terms, this means: if your website is too slow, you lose two-thirds of your potential customers. Just like that.
Performance is not a nice-to-have
I optimize every website I build for speed. With Vue.js and Nuxt 3, I have the right tools for this. Server-Side Rendering ensures that the first content is displayed at lightning speed. Code-Splitting means that only the parts that are currently needed are loaded. And modern image formats like WebP reduce the amount of data without any visible loss of quality.
A practical example from my work: a customer's website originally had a loading time of 4.5 seconds. After optimization, it was 1.2 seconds. The result? The bounce rate dropped by 40%, the dwell time increased by 25%. These are not abstract numbers – these are more satisfied visitors and more sales.
Mobile First is non-negotiable
73.1% of users leave websites that are not responsive. And Google? They already switched completely to mobile-first indexing in 2020. This means: Google primarily uses the mobile version of your website for rankings.
What does that mean for you? Your website must work just as well on a smartphone as on a desktop. Not just work somehow – work really well. Buttons must be reachable with the thumb. Texts must be legible without zooming. Forms must be easy to fill out.
I generally develop Mobile First. This means that I first design for small screens and then expand for larger ones. This is how I ensure that the most important functions are also perfectly accessible on the smallest device. With over 68% of web traffic from mobile devices, you can no longer afford to make compromises here.
Accessibility makes the difference
A good website works for everyone. Period. This means: contrasts must be right so that people with visual impairments can recognize the content. Images need alternative texts for screen readers. The navigation must also work with the keyboard.
Accessibility is not only ethically right – it is also economically sensible. You reach more people, your SEO improves (Google loves accessible websites) and you show that all users are important to you. In my projects, accessibility is not an additional feature, but standard.
Collaboration with designers and customers
"I work closely with designers." You read this sentence often. But what does that mean in concrete terms?
For me it means: I am there from the very beginning. Already during the design process, I look at the drafts and give feedback on the technical feasibility. Not everything that looks good in Figma can be implemented 1:1 – at least not performantly. Together we then find solutions that are both creatively and technically convincing.
A designer once designed a complex animation that was supposed to react to every scroll event. Technically feasible? Yes. But the performance would have suffered. So we sat down together and developed an alternative that looked just as impressive, but didn't slow down the website.
My role in the project
I translate between design and technology. When a designer talks about "this light shadow with 20% transparency", I know what is meant and how to implement it. When a developer talks about "API endpoints", I can put that into understandable words for you.
This bridging function is particularly important when communicating with you as a customer. You don't need to know what Vue.js is or how CSS Grid works. You want to know: Does my website work? Does it look good? Can my customers use it? I will answer exactly these questions for you – clearly, understandably and without technical jargon.
What you can expect from me
Transparency is my top priority. You will receive regular updates on the project progress. If something takes longer than planned, you will find out immediately – with an explanation and a proposed solution.
I work with Git for version control. For you, this means: every change is documented and can be undone if necessary. You can view the current status at any time, and we can decide together which features will be implemented next.
After development, I test on different devices and browsers. iPhone, Android, Chrome, Firefox, Safari – your website must work everywhere. And if you have special requirements (for example, support for older browsers), we will discuss this beforehand and I will plan it in.
Typical project flows
Every project is different, but the basic process remains similar. Let me show you what a typical collaboration looks like.
We start with a conversation. You tell me about your project, I ask questions. Do you already have designs? Is there an existing website? What are the most important functions? Based on this conversation, I will create an offer for you with a realistic timeframe.
Timeframes for different projects
A simple landing page? I can implement that for you in 3-5 days. A complete company website with 10-15 pages typically takes 2-3 weeks. For larger projects with special functions (online shop, booking system, member area), expect 4-8 weeks.
These times do not only include pure programming. I also plan time for feedback rounds, for tests on different devices and for fine-tuning. It's better to plan a few extra days and then finish earlier than the other way around.
What I deliver
You don't just get a finished website. You get the complete, clean source code. A documentation that explains how everything works. Access data to all relevant systems. And an introduction on how you can make smaller changes yourself.
The code I write is maintainable. This means: if you need a new function in a year, I (or another developer) can easily add it. No cryptic variable names, no nested functions that nobody understands. Clean, documented code that will also work in the future.
Aftercare
Our collaboration does not end with the handover of the website. I am also available for questions afterwards. Minor adjustments? No problem. A new feature? Gladly, let's talk about it.
Many of my customers book a maintenance package. This means: I take care of updates, monitor performance and am your contact person for all technical questions. You concentrate on your business, I keep your website running.
Let's talk about your project
You've made it this far – that shows me that you're serious about your website. That's great!
Now the question is: does what I offer fit what you need? The best way to find out is to have a conversation. Don't worry, I'm not a salesperson who wants to talk you into something. I'm a developer. I'll tell you honestly if I'm the right person for your project.
Frequently Asked Questions
ing"}]'} ::