Skip to content
nexapps — home

The platform came first. The apps are built on top of it.

nexapps is an AI-first mobile app studio. It is being built in an unusual order — the shared platform first, the apps on top of it — because that order costs more before the first app and much less on every app after it.

Who is building it

nexapps is Furkan Tanrıöver. Six years as a software engineer, most recently at AI mobile app companies, where the same five problems — identity, entitlements, the model call, analytics, and where private data stops — were solved again from scratch for every new app. nexapps is the attempt to solve them once and then build products on top of the answer.

Today the studio is one person. The platform is what the next person here would inherit on their first day, instead of building it again.

Where things stand on hiring

Where things actually stand

  • One app

    Pausa, and it has not launched

    A perimenopause symptom journal that turns a two-minute daily check-in into one clear sentence about the week and a report you can hand a doctor. It is built. It is not in a store.

  • One platform

    Built, and in use

    Sign-in, subscriptions, AI, analytics and privacy, built once for every app: native on iPhone and Android, with one Python server behind them. The first app runs on it.

  • No numbers

    Nothing to publish yet

    No downloads, no revenue, no case studies, because nothing has reached the public. When there is a figure worth publishing it will be a real one, and it will be possible to check.

Every decision dated, and none of them rewritten.

No funding rounds and no office openings — this is the only history the studio has, and all of it is written down before it is acted on.

  1. 2026-07-06
    ADR-0001 – 0009    The stack is decided in one sitting, in writing.Native Swift and Kotlin over cross-platform. FastAPI over Go. A submodule workspace over a monorepo. Entitlements built so that where a payment came from is a value they store rather than a system they depend on. An AI gateway with the keys on the server. Self-hosted infrastructure with a nightly encrypted backup from the first day it existed. Nine decisions, each with the argument that produced it and the cost it accepts.
  2. 2026-07-11
    ADR-0011 – 0013    The studio gets its permanent name, and its first app.Pausa cleared the spec gate and became the first app. The studio was renamed to the name it will keep — done deliberately before anything had been published, while the old name still existed only in internal code. And each app became its own repository, with the shared platform graduating to a versioned package rather than a folder apps copy from.
  3. 2026-07-12
    ADR-0013 executed    The platform ships as a package, not as a folder.The shared iOS code got its first version number, and the first app started depending on it like any other library. That is the moment the word “platform” stopped being an intention and became something with a version number that another app could adopt.
  4. 2026-07-30
    ADR-0015 – 0018    Four decisions, and one of them is “not yet”.The Apple developer identity was recorded as deliberately open rather than quietly assumed. No submission date was committed, and re-committing to one was made to require a new decision. The co-founder search was deferred with a written exit criterion — a restored backup, an alert someone has watched arrive, and no remaining irreversible single click.
  5. 2026-08-18
    ADR-0019    One site, many products — and the URLs are locked first.The address shape for every future product and every legal document was decided before the first one was published, because those addresses go into App Store Connect and outlive the code that serves them. Terms are studio-level; a privacy policy is product-level and cannot be shared, because it has to name the actual data, purposes and recipients of one product.
  6. 2026-08-23
    ADR-0020    The identity question closes.Incorporate a limited company and enrol with Apple as an organisation, so the App Store shows the studio rather than a personal name, and the founder's home address never becomes a published trader detail. This site went live the same day.

The log records its own corrections in place, including a pricing premise that turned out to be wrong and every figure derived from it. A decision that is deliberately not taken yet carries a status of its own, so the gap is visible instead of assumed away.

How the work is done

Specs before code. An app concept is written up and has to clear a bar before a line of it is built. Nothing gets made because it seemed interesting on a Tuesday.

Platform before product. If two apps would need it, it belongs in the shared foundation. The apps stay deliberately thin.

Privacy is architecture. The line between a phone and a server is drawn in code first and described by the policy second — never the other way round.

Claims have to be checkable. There is no download counter on this site for the same reason there is no logo wall: there is nothing true to put there yet, and something untrue would be trivial to disprove.

Every verdict is written down. Each app carries kill-or-scale thresholds fixed in its spec before the build starts, and whatever happens produces a written note that feeds back into the platform and the playbook. No moving goalposts mid-flight.

What is next

  • Pausa ships first. No submission date is committed, and that is a recorded decision rather than an omission.
  • Then more apps. Each one starts at the product, because everything underneath it is already there.

Pausasupport@nexapps.co

One person, one platform, one app that has not launched.