Skip to content
HS/24
Portrait of Hoang Son

00 · PROFILE / MOBILE SYSTEMS

Hoang Son

I make complex mobile systems feel clear.

Android · Compose · Design Systems · Ho Chi Minh City, Vietnam

A mobile engineer shaping reliable product experiences from the component API to the final interaction. I care about the details teams reuse and the moments customers remember.

Since 2019, I have built mobile products across Android, iOS, Flutter, and React Native. Today I focus on Android and Jetpack Compose at TymeX, connecting design and engineering through reusable components, clear guidance, and reliable quality workflows.

Based in
Ho Chi Minh City
Building since
2019
Current focus
Compose design systems
Working across
Product · Design · Engineering
Start a conversation ↗Read the CV ↓
01

Experience

2019—NOW

Building foundations, not just features.

My work sits where product engineering meets systems thinking: reusable UI, mobile architecture, release confidence, and the small decisions that help teams move well.

  1. TymeX ↗

    Software Engineer · Android Design Systems

    Building banking experiences and the shared Android foundations behind them.

    • Modernized legacy partner-portal flows for GoTyme Bank and Tyme Kiosk, moving core structures toward cleaner architecture.
    • Own the Origination & Customer domain, including registration and onboarding improvements for a large-scale banking product.
    • Lead the Jetpack Compose design system used by feature teams across products and markets.
    • Established component guidelines, a playground app, and snapshot testing to improve alignment and prevent visual regressions.
    • Deliver payment enhancements, production support, stability improvements, and workflow automation with n8n.

  2. Atmaneuler ↗

    Mobile Developer

    Delivered warehouse applications for manufacturing teams with complex material flows.

    • Built a Flutter import and export management application for Kstar using the GetX pattern.
    • Developed PungKook WMS in Kotlin with MVVM to manage warehouse flows for cloth materials.
    • Developed Hwaseung DPS in Kotlin with MVVM to track leather-shoe materials through import and export operations.

  3. THLOne ↗

    R&D Developer

    Researched and shipped products across mobile, desktop, and backend platforms.

    • Built iOS and macOS remote-viewer applications using the RDP protocol.
    • Developed an e-commerce backend for stores, delivery, and customers using REST APIs, RabbitMQ, MariaDB, and MongoDB.
    • Created an Android application in Java and MVVM to scan nearby beacons and display device information.
02

Selected projects

4 BUILDS

Experiments with a job to do.

Personal builds across Android, cross-platform mobile, and product interaction.

03

Writing notes

DEV.LOG

Notes from the workbench.

Occasional writing about mobile engineering, product craft, and what I learn while building.

  1. W—01Day 10/100: Looper, Handler, MessageQueue — The Machinery Android Runs OnCoroutines are how we write async code today. But underneath them — underneath everything in Android — is a 15-year-old threading model that's still running every single app. Understanding it changes how you debug, optimize, and reason about Android.
  2. W—02Day 9/100: onSaveInstanceState vs ViewModel vs SavedStateHandle — Pick the Right ToolThree mechanisms, three different guarantees. Using the wrong one means either losing state when you shouldn't, or over-engineering when you don't need to. Here's the complete decision framework.
  3. W—03Day 8/100: Process Death — What Actually Happens When Android Kills Your AppProcess death is the most misunderstood lifecycle event in Android. It's silent, it's unpredictable, and it breaks apps that work perfectly in development. Here's what actually happens — and how to write code that handles it correctly.
  4. W—04Day 7/100: Week 1 Recap — 6 Android Fundamentals I Thought I Knew ColdWeek 1 of my 100-day Senior Android series is done. Here's what I covered, what actually surprised me, and the one question I couldn't answer confidently until Day 3.
  5. W—05Day 6/100: Context in Android — The Wrong One Will Leak Your Entire ActivityApplication, Activity, Service — three types of Context, each with different lifetimes. Using the wrong one is one of the most common sources of memory leaks in Android. Here's the rule of thumb that prevents 90% of mistakes.
  6. W—06Day 5/100: Intent, Task & Back Stack and Why launchMode is a trapTasks and back stacks are how Android manages your navigation history at the OS level. Understanding them explains bugs that feel impossible to reproduce — and why launchMode almost always causes more problems than it solves.
04

Mobile craft kit

SELECT A LAYER
LAYER 01 / ACTIVE

Compose systems

Component APIs, tokens, variants, guidance, previews, and snapshot tests that let feature teams move without losing consistency.