About
I'm the one who builds it — and the one you reach when it breaks.
Julian Schweizer, media informatics. There is no agency behind SchweizerleLab, just a person. That is not a shortcoming; it is why you never have to explain again what you explained last week.
Why design and engineering sit together here
Media informatics is exactly that intersection: half computer science, half human–computer interaction. In practice it means I don't just implement an interface, I can explain why it looks the way it does — and I don't let an interaction idea die on technical grounds.
Most providers can do one or the other. When both sit with one person, the most expensive friction in a project disappears:the handover between design and implementation.
What separates this from pure implementation
I operate what I build. Four systems currently run in production under my responsibility — with Docker, TLS, automated deployments, backups and uptime monitoring. That changes how you build: someone who gets the call at night makes different decisions than someone who closes the project at launch.
Two consequences are evidenced on this site: anSEO project where I found and documented my own mistake in my own closing audit — and the decision to discard four months of my own work because the analysis pointed elsewhere.
Background
Media informatics at the University of Regensburg, a bachelor's with media studies as a second subject, then the master's — I am writing the thesis now, submission is close. Alongside that, volunteering in the IT department of Studentenfunk Regensburg, the campus radio station of the university and the applied sciences university, where I look after the website.
SchweizerleLab is registered as a sole proprietorship. The company is the form in which I take on contracts — the work behind it is what I have been doing since I started building software.
What I work with
Web with TypeScript, Astro, Next.js and Svelte. Backend with Python and FastAPI, Node, Postgres and Redis. Mobile with Flutter and Android. Operations with Docker, Traefik and Caddy, GitHub Actions, Hetzner. Plus WordPress when that is genuinely the right answer for the client — which is more often than developers admit.
The list is not a self-description but what actually runs in the systems linked from this site.