For years, most of what we learned while building software stayed inside the studio — in retrospectives, code reviews, and long conversations over coffee in our Berlin office. With Insights, we are finally opening that notebook.
What this blog is
Insights is where we write about the practice of building digital products: web platforms, mobile apps, AI features, and the EU-funded research projects we contribute to. Expect three kinds of posts:
- Engineering notes — concrete technical write-ups from our projects, including the mistakes.
- Project stories — how an idea became a product, from first workshop to launch.
- EU project dispatches — what we learn coordinating and disseminating Erasmus+ and other funded projects.
What it is not
We won't publish content for the sake of publishing. No recycled listicles, no "10 trends for next year". If a post doesn't teach something we genuinely wished we had known earlier, it doesn't ship.
Three languages, one voice
preunec works across Germany, Türkiye, and European consortia, so Insights is written in German, English, and Turkish. Posts may appear in one language first and get translated as we go — if you see a note that a translation is pending, check back soon.
If a topic resonates, or you disagree with something we wrote, tell us. The best posts here will come out of those conversations.
More posts
Devlog: rebuilding preunec.de
We rebuilt preunec.de from the ground up. Here's what changed for you as a visitor — and a friendly peek under the hood at how it works.
ReadHow we build mobile apps: a Clean Architecture playbook for Expo
The architecture we use for every Expo app — layers with a strict dependency rule, manual DI, feature modules, and a workflow that lets two developers move fast without stepping on each other.
ReadTurning a Website into Modules You Can Switch Off
How this site's sections became runtime-toggleable modules — and why that's worth the plumbing.
Read