Software Engineer · İzmir, Türkiye

Two platforms.
One behaviour.
Shipped fast.

Native iOS and native Android, the React web around them, and the C# services underneath. From design to release, and the maintenance after it — turn-by-turn navigation, CarPlay and Android Auto, offline data and KVKK / GDPR compliance included.

Start a project What I do

Services

The whole chain, or a single link

Most people do one link in this chain and hand you the rest. I do all of it, which is why the parts fit together. Come in wherever you need to.

  1. 01Idea and product shapingTurning a rough idea into a scope somebody can actually build and price. What ships first, what waits, what to cut.
  2. 02Market researchCompetitors, store positioning, price band. Who it is being built for, settled before what gets built.
  3. 03Branding and identityName, mark, palette, type and the rules that keep them consistent once other people start using them.
  4. 04UX and UI designFlows before screens. Figma, designed against the real platform conventions rather than a template.
  5. 05Planning and sprint managementThe work broken into sprints, scope and schedule fixed. What lands when is known from the start.
  6. 06Native mobile developmentiOS in Swift and SwiftUI, Android in Kotlin and Jetpack Compose. Same person on both, which is why they behave the same.
  7. 07Cross-platform developmentFlutter when one codebase is genuinely the right call — and an honest answer when it is not.
  8. 08Backend and APIsC# and .NET services, REST contracts, SQL. Designed so the clients can be built against them without guesswork.
  9. 09WebReact and TypeScript front ends, marketing sites, admin consoles. The same product, on the surface people find first.
  10. 10Testing and UATUnit and UI tests, screenshot tests, user acceptance testing. Things break here rather than on the store.
  11. 11CI/CD and release engineeringPipelines that produce a signed, installable artefact every time instead of a build somebody does by hand on a laptop.
  12. 12Store distributionApp Store and Google Play submission, review, phased rollout. Rejections handled, not forwarded to you.
  13. 13Compliance and legal surfacesKVKK and GDPR, review guidelines, terms of service, privacy policies, data safety and privacy declarations.
  14. 14Maintenance, support and monitoringCrash triage, production monitoring, OS and SDK updates, store policy changes. The long tail after launch that nobody puts in the estimate.

Parity

How the two stay identical

A feature that behaves differently on each platform is two products wearing one name. Parity is the discipline, not the by-product.

iOS — native

  • 01Swift, SwiftUI, UIKit interop
  • 02Swift Package Manager, modular targets
  • 03Signing, provisioning, build configurations
  • 04App Store Connect, review, phased release
  • 05Privacy manifest and data disclosures

Android — native

  • 01Kotlin, Jetpack Compose, coroutines
  • 02Gradle modules and build variants
  • 03Keystore, signing, R8 configuration
  • 04Play Console, review, staged rollout
  • 05Data Safety form and policy compliance

Delivery

Where the work starts and stops

An app that cannot pass review does not ship, however good the code is. The release and compliance work is part of the same job.

Design

Figma. Flows before screens.

Build

Native mobile, React front ends, C# services.

Test & UAT

Unit, UI, and the round with real users.

CI/CD

Pipelines that produce a signed artefact.

Release

Submission, review, phased rollout.

Maintain

Crash triage, updates, the long tail.

Work

What I have been building

Named by sector rather than by product. The client work belongs to the clients; the platform is my own. What is not launched yet stays unnamed.

2024 – 2026 Commercial EV charging and route planning platformClient product, delivered under contract. Native iOS and native Android, with the web surfaces and backend behind them. Vehicle account linking over OAuth/PKCE with Tesla and Volvo, and live charging status. Live in production on the App Store and Google Play. Mobile and product lead — architecture, build, store submission and review, and maintenance, support and monitoring from release onwards. Client · E-mobility
2026 — Licensable modular application platformMy own product. A licensable modular application platform spanning iOS, Android, a .NET backend and web — the foundation is built once, and branded sector products ship on top of it: booking, e-commerce, fintech, health, media, social, delivery, IoT. Products reach the customer as private compiled packages rather than source, with licences issued and revoked from a single signing key. The products are usable by AI assistants — App Intents on iOS, AppFunctions on Android and an MCP server on the backend — behind one security model: reads run freely, writes need confirmation, sensitive and personal data is never exposed. Built to stop four codebases drifting apart, which is the failure mode I keep seeing. In development. My own product
2025 Fitness and personal-training platformA Flutter application for iOS and Android from one codebase, a React admin panel, and a serverless backend. Trainer-facing content tools and a client-facing app, with in-app purchases, in Turkish and English, released on both stores. Client · Health & fitness
2024 Cost management platformBuilt full-stack modules on an existing platform: Node.js API and React web client. Deployment through Bitbucket Pipelines, team workflow on Jira. Client · Enterprise software

Method

Agents that keep the thread

Built in-house

  • —A memory framework that gives coding agents real project context instead of guesswork.
  • —MCP servers exposing each codebase as a queryable surface.

Why it matters

  • —The difference between AI that completes a line and AI that carries a change across iOS, Android, web and backend without losing the thread.

Stack

What I actually work in

Not a wish list. Everything here is in a codebase I ship and maintain.

Languages

Swift · Kotlin · TypeScript · C# · Dart

iOS

SwiftUI · Swift Concurrency (async/await, actors) · Swift Package Manager · WidgetKit · App Intents · Live Activities · Core ML · Core Data · CarPlay

Android

Jetpack Compose · Kotlin Coroutines · Flow · Hilt · Room · SQLite · DataStore · WorkManager · Paging · Glance widgets · Android Auto

Cross-platform & navigation

Flutter · In-app purchases (App Store & Play Billing) · Google Navigation SDK (iOS and Android) · Google Maps SDK · Turn-by-turn

Backend

.NET · MediatR (CQRS) · Entity Framework Core · PostgreSQL · MongoDB

Web

React · Redux Toolkit · MUI · Tailwind CSS · i18next · Node.js · Leaflet

Cloud & infra

AWS S3 · AWS KMS · Google Maps Platform · Firebase (Auth, Firestore, Functions, Cloud Messaging, Remote Config, Analytics, Crashlytics, Performance Monitoring, App Distribution) · Cloudflare R2 · Docker · Sentry

Security

OAuth / OpenID Connect (AppAuth) · PKCE · JWT · Google Tink · SQLCipher local database encryption · Keychain

Architecture

Clean Architecture · MVVM · MVI · Microservices · Modularization at scale · Atomic Design · Container-Presenter

Design

Design systems · Figma · Wireframing · Design tokens · Theming · Human Interface Guidelines · Material Design

AI

Agentic tooling · Claude Code · Model Context Protocol (MCP)

Testing

Roborazzi screenshot tests · Robolectric · MockK · Turbine · Espresso · UIAutomator · macrobenchmark · ViewInspector · Maestro

Distribution

CI/CD · Fastlane · Azure DevOps · Bitbucket Pipelines · Phased rollout

Compliance

App Store Review Guidelines · Google Play Policy · KVKK · GDPR · Data safety declarations