English · 한국어

15+ years of Android Native Development
Clean Architecture · Pragmatic Engineering · Products that ship 🚀

• 📱 Android Native Developer with 15+ years of experience
  • Hands-on across the entire evolution: Java → Kotlin → Jetpack Compose
• 🧩 Strong focus on Clean Architecture / MVVM / MVI
• 🎨 Product-minded engineer who values UI/UX as much as code quality
• ⚙️ Currently expanding into Embedded systems (STM32) and Rust
  • To better understand how things work beneath the abstraction layers
• ✍️ Enjoys documenting, writing, and sharing practical knowledge

“Code is a tool.
Building sustainable products is the goal.”

From the early days of my career,
I was never satisfied with simply shipping features fast.

Working on long-lived Android products, I repeatedly encountered:

• Growing and tangled codebases
• UI changes becoming increasingly expensive
• Maintenance costs quietly dominating development time

That led to a simple realization:

The real problem was rarely the code — it was the structure.

Since then, my focus has shifted to asking better questions:

• Why does this layer exist?
• Where should this dependency truly belong?
• Will this decision still make sense a year from now?

Recently, I’ve been extending my perspective beyond mobile by studying
Embedded systems and Rust, aiming to become an engineer who understands not only how to build on top, but also how systems work underneath.

My personal standard remains unchanged:

✨ Code should be understandable today,
resilient tomorrow,
and maintainable by the next engineer.

• Android SDK (API 21+)
• Jetpack Compose & View System
• Coroutines / Flow

• Clean Architecture
• MVVM / MVI
• Multi-module Gradle (Kotlin DSL)
• Testable & maintainable codebases
• Dependency Injection (including DI-free designs)

• 🦀 Rust
• 🔌 Embedded systems (STM32)
• 📐 System design & performance optimization

• ✨ Advancing Jetpack Compose-based UI architectures
• 🧪 Designing reusable Android core / network / domain modules
• 🧠 Learning low-level concepts to broaden system-level understanding
• ✍️ Writing and organizing practical engineering knowledge

• 🧱 Architecture exists to support change, not to show off
• 🧪 Testability is a design decision, not an afterthought
• 🎨 UI is part of the system, not decoration
• 📦 Reusability matters only when it solves real problems
• 🚀 Shipping matters — but never at the cost of maintainability

“Good engineers write code.
Great engineers design for tomorrow.”

I value how systems are designed more than raw numbers.

• 🧩 Android Architecture Templates

  • Clean Architecture-based Android project structures
  • Multi-module · Compose-friendly · Testable
  • (Private / Work in Progress)

• 🧪 Reusable Android Core Modules

  • Clear separation of Network / Domain / UI layers
  • Continuously refined with real-world constraints

• ⚙️ Embedded & Low-level Experiments

  • STM32 and Rust learning projects
  • Exploring systems beyond mobile applications

• GitHub: @dreamboy1339
• LinkedIn: learning about unlearning
• X(ex. twitter): Fog
• Blog: dreamboy1339

Structure over numbers.
Sustainability over speed.
Building products that last.