About

I am a product engineer in İstanbul. I started on the front end: HTML, SCSS, then Vue, then React, and kept walking backwards into the parts that decide whether a product survives: the types at the edges, the deploy, the one field name that is wrong only at runtime.

In 2026 that became koative, an independent software studio. It ships its own products first and takes a few client projects a year, which is the arrangement that keeps the judgement honest: nobody else’s deadline decides what our own app is allowed to be. The first product is Lumi, an iOS app built around a single daily ritual rather than a dashboard.

My bias is toward less: fewer screens, fewer dependencies, fewer settings nobody will ever open. I would rather ship a boring service that survives a year unattended than a clever one that needs me awake. Most of my writing is an argument with a younger version of myself who thought clever was the point.

Rules I work by

• Types live at the edges. A typo in a field name should fail tsc, not production.
• One artifact to deploy. If it takes a runbook, it is not finished.
• Every dependency must justify its own line in the lockfile.
• Ship less, then spend the saved time on the details people actually feel.

Working together

koative takes on a few client projects a year: iOS and Android apps, web platforms, and the product design in between. Best fit: a team that would rather cut scope than cut care.

Mail id@koray.dev. Replies within 48h.