Ahmet Ablak

Istanbul · Flutter developer

I ship mobile products. And the systems that keep them shipping.

Four years of production Flutter across e-commerce, industrial IoT and real-time apps. I plan the refactor, set the standard, fix the pipeline, and take the app from idea to store.

Get in touch See the work
  • <1sLoad time of data-heavy screensfrom 1.5–2 s
  • 15 minNew project bootstrapfrom 1–1.5 weeks
  • −10%Codebase size after refactor plan
  • 4+Apps shipped to the stores
Selected work

Problems I was trusted with, and what changed after.

Store links are public; the engineering behind them is below.

01 · High-traffic app · 2025–26

Refactoring a live, real-time app without stopping it

A high-traffic consumer app with live data and heavy daily traffic.

Problem

Years of feature pressure left duplicated classes, dead layers and a core widget set that no longer matched the design. Data-heavy screens took up to two seconds to open.

What I did
  • Ran a technical-debt analysis and turned it into a sequenced refactor plan the team could execute alongside feature work
  • Rewrote the screen architectures that could not carry the new requirements
  • Planned Design System v2 with the design team and migrated the app to it
  • Made lint and analysis rules mandatory so performance stopped depending on who wrote the code
  • Repaired store and environment configs so CI/CD delivered reliable releases
Result

Codebase ~10% smaller, heavy screens under one second, crashes down to a minimum.

02 · Industrial IoT · 2023–25

Talking to industrial pumps over a custom Bluetooth protocol

Caerus — mobile control of Wilo pumps in the field, built at BosphorusISS.

App Store ↗Google Play ↗
Problem

BLE replies arrive out of order, on an unreliable link, with several commands in flight. Matching an answer to its question is the whole problem.

What I did
  • Designed a correlation-ID based command/response layer on top of streams
  • Handled timeouts, reconnects and partial frames as first-class states, not edge cases
  • Kept the protocol code isolated so UI work never touched byte handling
// Every command gets an id; the reply stream is
// filtered by it, so answers never cross wires.
Future<Reply> send(Command cmd) {
  final id = _ids.next();
  final reply = _incoming
      .where((f) => f.correlationId == id)
      .first
      .timeout(const Duration(seconds: 3));
  _channel.write(cmd.encode(id));
  return reply.then(Reply.decode);
}
Result

Stable device control in field conditions, with failures surfaced instead of hidden.

03 · Developer platform · 2023–25

From a week and a half to fifteen minutes

BosphorusISS — an agency starting new Flutter projects every few weeks.

Problem

Every new app began with 1–1.5 weeks of copying architecture, wiring CI and re-creating the same widgets by hand.

What I did
  • Wrote a project template that scaffolds the base architecture from app name, package name and module choices
  • Built company-wide CI/CD on Azure Pipelines, Appcircle and GitHub Actions with automated build scripts
  • Packaged the company's shared widgets into libraries served from the internal package registry
Result

Project bootstrap dropped to 15–30 minutes, and every team started from the same standard.

04 · Own product · 2026

Masruf — a budget app, from idea to revenue

A personal-finance app I built and published with a partner, outside of work.

App Store ↗Google Play ↗
Problem

A two-person side product means owning everything a company team usually splits: product, subscriptions, sign-in, and a long App Review process.

What I did
  • Subscriptions and in-app purchases through RevenueCat, plus a promo-code system
  • Google and Apple sign-in, with iPad layout parity for App Review
  • Worked through several review rounds to approval on both stores
Result

Live on the App Store and Google Play, with real purchases coming in.

On the stores

Apps I worked on that you can install today.

Internal and client systems (MES, smart-home, admin panels) are not public. Happy to walk through them in a call.

Experience

Four years, three teams, one habit: leave the codebase better.

Aug 2025 – Aug 2026

Path Teknoloji

Flutter Developer

  • Tech-debt analysis, refactor plan and Design System v2 migration
  • Root-caused third-party SDK issues; shipped native iOS/Android workarounds
  • Authored the team’s AI-assisted development guidelines
  • Technical interviews for Flutter hires; onboarding and environment setup for new members

Nov 2023 – Jul 2025

BosphorusISS

Flutter Developer

  • Caerus BLE app for Wilo pumps
  • Company-wide CI/CD and a project template (bootstrap: weeks → minutes)
  • Moved a smart-home app (doors, alarms, shutters) to Firebase cloud messaging at no extra cost
  • Flutter Web MES platform, supervisor alerts, operator and tablet apps, logistics POCs

Sep 2022 – Nov 2023

Path Teknolojiİdefix

Junior Flutter Developer

  • Complex UI and state management for a large e-commerce app
  • Owned App Store and Google Play releases
  • Trained two interns and brought them onto the project
Toolbox

What I reach for.

Platform
Flutter (iOS, Android, Web), Dart, platform channels
Architecture
Clean Architecture, Bloc / Cubit, GoRouter, design systems, lint rules
Backend
Firebase (Auth, Firestore, FCM, Functions, Crashlytics), Supabase, REST
Delivery
GitHub Actions, Azure Pipelines, Appcircle, Docker, Nginx
Observability
Sentry, New Relic, Azure App Insights, Firebase Analytics, Adjust
Revenue
RevenueCat, in-app purchases, subscriptions, ad SDKs
Devices
Bluetooth Low Energy, custom protocols, IoT over Firebase
Stores
App Store, Google Play, Huawei AppGallery — release and review
Now

Building AXAND.

In 2026 I founded AXAND, a product design and engineering studio in Istanbul.

Same standards as this page, applied end to end: design, mobile, web, backend and the store, with one team and no hand-offs.

AXIS + AND

Currently building
AI · Mobile

A lab-analysis app: guided photo capture, a custom-trained detection model that counts colonies, results in seconds.

Web · Marketplace

A verified household-services marketplace with vetting, badges and explainable matching.

Background

Engineer first, planner by habit.

The work I enjoy most is the part before the code: breaking a messy system into tasks, estimating them, and getting a team to agree on the order. I pitched my first refactor plan myself and ran it end to end.

I studied Computer Technology and Information Systems at Trakya University, where I wrote C#/.NET desktop apps, Django sites and a few TensorFlow experiments before settling on Flutter.

Education
Trakya University · Computer Technology & Information Systems, 2023
Languages
Turkish (native) · English (B2)
Outside work
Built an ESP32 airsoft game controller · licensed-radio exam prep · cooking
Contact

Let’s talk.

[email protected]
Email LinkedIn ↗GitHub ↗

Remote roles, freelance mobile work, or a technical second opinion. Email gets the fastest answer.