Products

Things I build.

Products are decisions carried into behavior, systems, and the details people eventually depend on.

Personal products

Built with direct responsibility.

Personal / In production

PersonalIn production

EDIP

Concept visual for EDIP, a local-first conversational video editor.

An AI-oriented video editor for creators.

Bring raw footage, describe the result you want, inspect the edit, and revise it conversationally. EDIP keeps source media and project ownership local while treating every edit as a controlled, non-destructive step. The goal is not to turn editing into a black box. You should be able to understand what changed, ask for another direction, and keep moving without rebuilding the whole timeline by hand.

  • Local-first
  • Chat-driven
  • Non-destructive
  • AI-oriented end-to-end editing

Designed and built by Mehmet Arslanca.

Devonair products

Software, products & systems.

I also build as part of Devonair, the software, products, and systems side of Ebiren. Shared products stay explicitly shared; collaboration does not erase ownership.

Visit Devonair

Devonair / Shared product / In development

DevonairIn development

Concept visual for IT’S SO OVER, a local-only Android behavior and reality-check product.

IT’S SO
OVER

Local-only behavioral reality checks.

IT’S SO OVER is a local-only Android product built around behavioral reality checks. A constrained set of permissioned device signals is turned into on-device behavioral context, then used to decide whether a timely nudge is worth making and which curated message actually fits the moment.

Its tone is deliberately dry and sharp. It makes the behavior visible without pretending to know more about the person than the device can actually support.

Built by Mehmet Arslanca and Murat Bahadır Kayıhan.

  • Android
  • Local-only
  • Behavior-aware
  • Curated reality checks
View on Devonair

Broader ecosystem

Devonair.

An honest postmortem

Not everything survives.

PersonalArchived

OrchestrAI

This one didn’t make it.

This one didn’t make it. OrchestrAI explored serious LLM and provider orchestration through a production-minded backend. The original question was real: how could a product coordinate providers and models without coupling its behavior to any one of them? Authentication, persistence, streaming, and orchestration were treated as parts of one coherent system rather than a disposable demo. The ecosystem then moved quickly enough that parts of the original value were implemented or commoditized elsewhere. Continuing would have meant spending more time defending an old premise than solving a useful problem, so I archived it. Stopping was the better product decision.

Its backend was treated seriously, but the reason to keep building it weakened. Archiving it was the point where the product decision became clearer than the implementation momentum.

Technical footprint

  • Java 21
  • Spring Boot
  • PostgreSQL
  • Redis
  • Flyway
  • JWT/auth
  • SSE
  • Docker
  • LLM / provider orchestration

Experiments / earlier work

Kept in context.

MangaMuse

PersonalLearning-era

An earlier Android learning project kept here because it belongs to the path, not because it represents my current product work.

Android / Kotlin

GeoCall

PersonalExperiment

A small local automation experiment for monitoring a remote backup device’s location and sending Telegram notifications from configurable geographic zones, replacing a manual check with a private local tool.

Python / SQLite / Telegram bot / systemd / Local scheduling / Geographic zone logic