Websites, online stores and apps, built from plan to launch.

I'm a software developer who runs your project from start to finish: planning, development, launch and maintenance. E-commerce sites, iOS and Android apps, web apps and online products, and automations that connect your tools.

What I do

  • E-commerce websites

    Online stores built to your brand, usually on Shopify, including moving an existing store over with its products and content.

    See Kremi's online store

  • Mobile apps

    iPhone and Android apps, built once for both and published on the App Store and Google Play.

    See the Kremi app

  • Web apps and SaaS

    Online products people sign in to and pay for, built from the first screen to launch.

    See PromptLikeEngineer

  • Automation and integrations

    Marketplaces, shipping, stock and email connected, so orders are not copied between tabs and anything that fails raises an alert.

    See Kremi's order systems

  • End-to-end project management

    One person from the first plan to after launch: a written scope, regular written updates, and the same developer still there once it's live.

    See how I work with Kremi

  1. 2025 – present

    Software consultant

    Kremi, cosmetics e-commerce

    The Shopify storefront, the iOS and Android app, and the order systems behind them, worked on month by month.

  2. 2026 – present

    Freelance engineer

    Clients abroad, remote

    Took over a live restaurant platform and moved its database to PostgreSQL while it stayed online, for a client who came back with more work.

  3. 2025 – present

    Independent practice

    Own products and client work

    PromptLikeEngineer, LinkZae and FolderPls are live; an open-source CLI and MCP server are on npm; white-label sites run for clients.

  4. 2020 – 2024

    B.Sc. Computer Engineering

    Kocaeli University

    Graduated in June 2024, with a part-time developer role at the university and two internships along the way.

Selected work

All work

For Kremi, a cosmetics brand, I build and look after the app and the systems behind the orders, and develop the online store. Then products I build and run myself.

Mobile app, 1 of 6

Software Consultant · Kremi

Still from the abstract animation of Kremi's operations systems, with no real screens or data: orders from the online store and three marketplaces flowing into one queue, then email notifications, shipping, reviews, returns and the operations panel that ties them together

Kremi · Operations

Operations systems

The systems behind Kremi's orders: the online store and three marketplaces feeding one queue, shipping labels, returns, reviews and email, with failures raised as alerts. They are internal, so they are drawn, not shown.

Still from the animation built from screens of the FolderPls panel with invented sample files: AI tagging started with a button, labels appearing on Drive files, then the files mapped in a graph

Public beta

FolderPls

Organizes Google Drive files with tags laid over your existing folders, so nothing has to be moved.

Developed together with Erkut Yıldırım.

Still from the animation built from LinkZae's own interface, as shown on its site: a digital business card designed, its QR code printed and the contact saved

Live

LinkZae

Digital business cards and link pages, each on its own subdomain, shared by link or QR code.

With thanks to the friend who started this with me and helped get the first version off the ground.

More of my own systems

More systems I build and run outside client work.

Other client work, in depth

Inherited system modernization · Brand kept confidential

Finding the silent data loss in a platform I inherited

The panel said “commission updated”; row-level security had silently rejected the write. It was the most valuable find of a five-month live migration.

Read the case
5months with the system live while the database was replaced

What that means in practice

  • Tenant isolation

    A customer's data boundary holds even if the application code forgets to check. Permissions live in the database, so a query written wrong returns nothing rather than someone else's rows.

  • Durable work

    A job that fails does not disappear. It retries, and if it keeps failing it lands in a dead-letter queue and tells a human it gave up, instead of leaving a gap nobody notices until a customer calls.

  • Ledgers that cannot drift

    Balances are derived from an append-only history, not stored and updated in place. There is no path where the number on screen and the events behind it disagree.

  • Keys that stay on the server

    The browser never holds a backend credential. Every call to a payment or marketplace API goes through a server-side route, so a leaked key is not one view-source away.

  • Releasing, not just building

    Apps taken through store review and released on both the App Store and Google Play, including the parts nobody demos: forced updates, crash reporting, and what the app does with no network.

  • Inherited systems

    Reading a codebase I did not write and finding the assumption buried in it, then migrating its database while the business keeps running on it.

White-label sites

Sites running on one white-label site platform I built: a shared database and a clonable template.

How a project runs

  1. Plan

    You tell me the goal. Before any work starts, you get a written scope and an estimate.

  2. Build

    I build in small steps and send a written update at the end of each working block, so you always know where it stands.

  3. Launch

    The site or store goes live, and apps go through App Store and Google Play review to release.

  4. Care

    After launch I stay on for fixes, updates and whatever comes next, per project or month by month.

Have something to build, or something to fix?

A new website, store or app, or a project someone else started? Tell me what you have and I will tell you where I would start.

Agencies: white-label under NDA