SOFTWARE & DIGITALISATION · FRONTEND DEVELOPMENT
Frontend Development in Dresden. Maintainable Interfaces.
Component-based web applications with React, Angular and TypeScript. Clearly structured, fast and testable — with attention to crawlability when SEO matters.
How the Elements Connect
- Components
- Types
- Rendering
- Tests
Typical Starting Points
- An existing application is growing, but the codebase is becoming unmaintainable.
- Build times are increasing sharply, and tests are missing or unreliable.
- Frontend performance is poor without a clear cause.
- The SPA renders an empty page for Google, and nobody checked before launch.
The Focus of Frontend Development
Frontend development focuses on client-side implementation and its architecture. The work covers components, state management, rendering, tests and accessibility, both when building an interface and improving an existing codebase.
The Service in Detail
Architecture & Types
- Component Architecture
- A clear separation of containers, views and state. A design system rather than uncontrolled growth.
- Strict TypeScript
- End-to-end type safety, including backend API types — no unjustified use of `any`.
Rendering & Performance
- Performance Tuning
- Bundle analysis, code splitting, lazy hydration and controlled rerenders.
- SSR & Prerendering
- Next.js, Nuxt, Astro or Angular Universal — depending on the stack.
Testing & Accessibility
- Tests
- Vitest/Jest for unit tests and Playwright for end-to-end tests. CI integration with quality gates.
- Accessibility
- WCAG 2.1 AA, keyboard navigation, screen reader testing and axe-core in CI.
The Approach
Audit
Codebase review, architectural assessment and performance profiles.
Plan
A refactoring roadmap with quick wins, structural work and long-term architecture.
Coding
Pair programming or feature-based delivery, always with tests.
Review
Thorough code reviews covering readability, security, performance and tests.
Handover
Documentation, onboarding sessions and, where appropriate, ongoing pair-mentoring sessions.
The Service Within Its Competence Area
The competence hub explains the wider connections. Frontend Development focuses here on the specific task.
Software & Digitalisation →Technical and Practical Foundations
- TypeScript
- React
- Next.js
- Angular
- Vue.js
- Astro
- Vite
- Playwright
- Storybook
Project, Handover and Ongoing Work
A Defined Project
In a defined project, we review component architecture, rendering and interface quality and agree the scope around the existing environment.
After Implementation
For the continuing work on Frontend Development, the existing process includes: Documentation, onboarding sessions and, where appropriate, ongoing pair-mentoring sessions.
Scott Nowak. Direct Collaboration on Frontend Development.
I am Scott Nowak, your direct contact for Frontend Development. We discuss component architecture, rendering and interface quality and connect the requirements with their implementation.
More About Scott →Questions About Frontend Development
Do you prefer new projects or existing codebases?
Both. New projects let us establish clear architecture from the outset. Existing projects are often more valuable because we can deliver measurable improvements: shorter build times, fewer bugs and better maintainability.
React, Vue or Angular?
It depends on the team and project. For SPA-heavy business apps with large teams: Angular or React with TanStack. For content-led sites with strong SEO: Astro or Next.js App Router. For smaller interactive tools: Vue 3.
How do you approach SSR and SEO?
We decide route by route: static content uses SSG, dynamic content uses SSR with a clear caching strategy, and interactive apps behind a login use CSR. This is agreed in the architecture workshop rather than based on intuition.
How do you measure frontend performance?
We use real-user monitoring, track Core Web Vitals for each route and define performance budgets in CI. Builds fail if the bundle grows — our performance gate.
Do you have experience with multilingual websites?
Yes, using react-i18next, next-intl and Angular i18n. We implement hreflang, locale-aware routes and SSR with the correct `Content-Language` header. Translations are often maintained with Lokalise or Crowdin.
Where does your frontend need a clearer structure?
Describe component architecture, rendering and interface quality. The existing project brief lets you share your starting point and supporting materials.
Would you like to speak first? →Response time: < 48 h
Project start: typically 2–4 weeks
Within 48 hours on business days.