Release-ready Flutter apps, and the fixes that got them there

I’m Muhammed Said Çakır. I run MSC Labs, a one-person studio in Türkiye, and I take Flutter apps from “works in debug” to “live in the store”.

Between September and October 2026 I built four products on one shared design system: two Flutter apps, a Cocos Creator game and a law-based calculator website. These case studies show the decisions behind them and the bugs that only appeared in release builds.

Case studies

Mesai Defteri

A Flutter app that counts overtime against the weekly limit in Turkish labor law, and a release-only crash caught before launch.

Flutter · Android · Google Play · 88 tests

Fatura Defteri

On-device bill scanning that never sends a bill anywhere, accuracy measured per field, and reminders that silently never fired, fixed.

Flutter · Android · On-device OCR · 188 tests

İş Hesaplama

A static Astro site where every calculator names the law article it implements, with no third-party requests and no cookie banner.

Astro · TypeScript · Static site · SEO

Harf Yolu

A Cocos Creator word game whose rules run in plain TypeScript under 151 tests, and a release-only freeze traced to the code shrinker.

Cocos Creator · TypeScript · Android · 151 tests

The shared foundation

One JSON token source styles two websites, two Flutter apps and a game; CI regenerates it, runs only what changed and enforces custom rules.

Design tokens · GitHub Actions · Monorepo

Work with me

  • Take a Flutter app from “works on my phone” to Play Store production: release builds, R8 and ProGuard rules, signing, Fastlane, store listing and the Data Safety form.
  • Find release-only crashes and silent failures: stripped classes, missing manifest receivers, notifications that never fire.
  • Build new Flutter features with tests: business logic kept out of the UI, golden tests for screens, tablet layouts.
  • Localize properly: Turkish İ and ı casing, font subsets, locale-aware numbers and dates.

How I work

  • A written plan before code, and a short progress note every working day.
  • Every change tested as a release build on a real device.
  • Fixed price or hourly. GMT+3, overlapping European working hours.

Email muhammedsaidcakir@msclabs.tr with what you need and the error log or build if you have one.