Skip to content

About

The platform came before the app. That is the whole thesis.

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.

  1. Who is building it
  2. Where things actually stand
  3. How the work is done
  4. What is next
  5. Getting in touch

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. That is a statement about today rather than a strategy: the platform is how one engineer ships at the pace this work used to need a team for, and it is what the next person here would inherit on their first day instead of building it again.

Where things actually stand

  • One app. Pausa: 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 has not launched yet.
  • One platform. A production backend, an iOS SDK, an Android SDK, server-owned entitlements, an AI gateway, first-party analytics and a privacy boundary — all built, and all in use by the first app.
  • No numbers to publish. No downloads, no revenue, no case studies, because nothing has reached the public yet. When there is a figure worth publishing it will be a real one, and it will be possible to check.

How the work is done

Specs before code. An app concept passes a written stage gate 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 SDK. 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.

What is next

Pausa ships first. The second app is the real test of the thesis — if the platform is what it claims to be, that app starts at the product.

Getting in touch

Questions, press or partnership: support@nexapps.co.

If you are wondering about working here, Careers says exactly where things stand.