Samuel Odukoya - Senior Flutter Engineer
Remote Flutter engineer

Hello I'm Samuel O.
Senior Flutter Engineer
Based in Nigeria

My favourite moment is the one right before the first commit—the repo is empty, the product pitch is still half in Notion, and someone needs to decide how this thing will actually ship. I love starting the codebase, sketching the module map, wiring CI, and writing the README the next engineer will lean on. I pair closely with founders, PMs, and designers to pick the battles, trim scope, and keep the first build fast without burying future velocity.

AfCircle is the latest example. The founders called on a Friday; by Sunday night I'd pushed the initial Flutter skeleton, named the packages, and left comments for the next day's standup. Over the following weeks I carved Kotlin camera pipelines so creators could film reels without dropped frames, threaded in an AI assistant that handled 40% of community replies, and shipped enough patches through Shorebird to keep 1,000 daily users happy inside three months.

I'm looking for a full-time remote seat with a team that spans time zones—North America, Europe, LATAM, MENA, APAC, anywhere people care about craft. If you need a founding-style Flutter engineer who can spin up the repo, coach the crew, and keep async updates honest, let's talk.

LinkedIn
WhatsApp
Twitter
Phone

My Skills

Flutter

Flutter

Dart

Dart

Kotlin & Java (Android Native)

Kotlin & Java (Android Native)

Platform Channels (Kotlin/Swift)

Platform Channels (Kotlin/Swift)

GetX & Bloc

GetX & Bloc

Provider Patterns

Provider Patterns

Firebase

Firebase

Shorebird OTA

Shorebird OTA

AI Copilots

AI Copilots

Git/GitHub

Git/GitHub

About Samuel Odukoya

About Me

I'm Samuel Odukoya—an electronics-and-computer-engineering grad who fell down the software rabbit hole during Harvard's CS50 back in 2015. I stubbornly stuck with mobile because I liked seeing ideas land in people's hands. The early days were pure Kotlin and Java, plenty of late-night logcat sessions, and a healthy respect for platform-specific quirks.

Flutter arrived in 2019 and instantly felt like the right canvas. I shipped my first production Flutter app that same year, learned how far you can push declarative UI before you need a platform channel, and started pairing the framework with Laravel, Firebase, or Next.js whenever the product needed extra muscle. Since then I've helped launch social apps, AI copilots, and fintech tools for teams spread across Lagos, Stockholm, Cape Town, and Austin.

When I join a team, I spin up the repo, write the first tests, set up the release pipeline, and make sure the README actually explains how to get a build running. I keep check-ins async-friendly, drop Loom videos for tricky flows, and leave behind docs so the next engineer doesn't need to DM me at 2 a.m. I'm the person who nudges design, product, and analytics into the same thread so we catch issues before sprint review.

Outside commits, you'll probably find me watching F1 replays or sketching UI ideas with a mechanical pencil—old habits from the hardware days. Professionally, I'm searching for a full-time remote team that wants a founding-style Flutter lead who can own the mobile roadmap, jump into Kotlin/Swift when the platform demands it, and keep the rest of the stack humming alongside the app.

Latest Blog Posts

Get In Touch

LinkedIn
WhatsApp
Twitter
Phone

Thank You!

Thanks for riding all the way to the footer. Hopefully these notes gave you a clear picture of how I approach shipping. If you want to jam on your roadmap, trade Flutter war stories, or drop a brief, my inbox is open and I usually reply same day.