Hi, I’m Dongmin Yu. You can call me Andrew.

I’m a cross-platform engineer based in Seoul. I build mobile apps with Flutter and React Native, work with Swift and Kotlin when a feature needs native code, and publish open-source libraries and developer tools.

This blog is where I write about the work behind those projects: the integration that needs a closer look, the migration that changes an assumption, and the small tool that grows out of a recurring problem.

If you build mobile apps, maintain packages, or take your own product from an idea to a release, those are probably familiar situations.

From kitchens to software

Before becoming a developer, I worked as a chef. My path into software began with teaching myself Python and web scraping, and eventually led to cross-platform mobile development.

These days, I work across app interfaces, native integrations, and the tooling that helps get a product into people’s hands. My projects include mobile apps, games, open-source packages, and developer tools. They give me plenty of reasons to keep learning—and plenty of problems worth writing about.

Where the interesting problems show up

Much of my work sits where different systems meet.

A TypeScript API needs to agree with a native implementation. An iOS capability needs a usable interface in Flutter. A library has to survive a framework upgrade. A release pipeline needs to publish the right package with the right permissions.

These boundaries turn into concrete questions. What exactly does this API promise? Which layer owns the behavior? What changed between versions? What can a test establish, and what still needs to be checked on a device?

Recent posts here explore questions like these through React Native’s New Architecture, Dart analyzer migrations, receipt scanning, and Flutter package publishing. The starting point is usually a specific problem. The useful part is understanding enough of the surrounding system to explain why the solution works.

Apps, libraries, and the work between them

I build and release my own apps alongside my open-source work. Those projects let me work through the full product cycle, including decisions that are easy to leave out of a small code example.

WarmWake, for example, is a Flutter alarm app built around voice messages recorded for the next morning. Prism Defense explores a different kind of mobile experience through a tower-defense game. I also work on native iOS projects.

Building products creates opportunities to extract reusable pieces. Sometimes the result is a package another app can use. Sometimes it is a tool that makes a recurring development task easier. Working on both gives me a chance to test an abstraction against the needs of an actual app.

This blog connects those two sides: making something people can use, and understanding the engineering that makes it possible.

What you’ll find here

I write about cross-platform development, native integrations, package maintenance, and developer workflows. That includes debugging stories, migration details, release automation, and tools built to address practical friction.

Some articles focus closely on one API or error. Others follow a broader workflow, from identifying the problem to checking the result. I try to keep the context visible: which version was involved, what assumption failed, and where the approach applies.

You don’t need to use every framework I use to follow along. A post about a Flutter package or React Native module can still offer a useful way to investigate an integration, design an interface, or check a change.

You can explore my projects on GitHub or visit my portfolio for a wider view of my work.

GitHub: https://github.com/AndrewDongminYoo Portfolio: https://www.donminzzi.kr

Thanks for reading.