Esma Gaygusuz
apps · apis · ai

Mobile apps,
from screen to server.

I design and build complete mobile products: iOS and Android apps, the backend APIs behind them, AI-powered features, in-app subscriptions, and the release process that gets them into the stores.

Tell me about your app$ explore the layers
  • iPhone
  • Android
  • Tablet
  • Backend APIs
~/projects/ship
$release --all-platforms
✓lint + typesclean
✓test suitegreen
✓ios archiveapp.ipa
✓android bundleapp.aab
→TestFlight → App Storein review
→Play Consolein review
$

// tools i work with

  • TypeScript
  • React Native
  • Swift
  • Kotlin
  • Node.js
  • PostgreSQL
  • Firebase
  • Redis
  • OpenAI
  • RevenueCat

01Layers

More than an app.
Everything it runs on.

Mobile client, backend, database, AI, and billing are planned together and released together, so no piece is left behind.

architecture.map

app.iosapp.androidapp.tablet
core.api
databasecacheaipaymentsnotifications

layer.mobile

Mobile apps

Cross-platform iOS and Android apps in React Native, with native code where it pays off: notifications, deep links, offline data, and tablet-friendly layouts.

  • React Native
  • Swift
  • Kotlin

layer.server

Server & APIs

Typed REST endpoints, authentication, background workers, and schema migrations that go out together with the feature they support.

  • Node.js
  • PostgreSQL
  • Redis

layer.ai

AI inside the app

Conversational assistants, structured responses, and live voice, with keys and product logic kept safely on the backend.

  • OpenAI
  • Realtime
  • Tools

layer.billing

Monetization & growth

Paywalls, subscription access, event tracking, and install attribution set up from day one, not bolted on later.

  • RevenueCat
  • Firebase
  • Attribution

layer.ship

Releases & stability

Store-ready builds, crash monitoring, and remote config, so every version after launch is better than the last.

  • CI
  • Crashlytics
  • Remote Config

layer.trust

Privacy & security

Secrets stay on the server, permissions stay minimal, and the privacy policy describes what the app really does.

  • JWT
  • OAuth
  • GDPR

02Workflow

Ship often. Learn from real users.

  1. 01./plan

    Plan

    Agree on the first version worth releasing and the data it depends on.

  2. 02./develop

    Develop

    App, backend, and schema changes land together. Typed, tested, and reviewed.

  3. 03./launch

    Launch

    Store submissions, review notes, and gradual rollouts on both platforms.

  4. 04./learn

    Learn

    Usage, crash, and revenue data decide what the next version brings.

03Contact

Starting a new app, or saving an existing one?

A fresh product idea, an app that needs fixing, or a question about something I built. Email reaches me the quickest.

mail

$ mail --to

info@esmagaygusuz.com

→ write an email

Reply time

Most emails get an answer within a working day.

new builds · app rescue