Kev's blog

How I Became an Android Developer While Studying Embedded Systems

When I first started learning about Embedded Systems, I didn't even think about developing for Android. I was really into microcontrollers, C/C++, and bare-metal programming, which isn't the same as apps, touchscreens, and user interfaces.
But at some point, that changed.

This is the story of how I went from doing low-level embedded programming to Android development with Kotlin and why I'm glad I did.

πŸš€ Phase 1: Going from Small Things to Big Things

Most of what we did in my Embedded Systems program was focused on hardware-close development.
Think bare-metal C, RTOS, I2C buses, and using oscilloscopes to debug.

I loved the control, the accuracy, and the predictability.

But I also realized that in many of my projects, the user experience was an afterthought. Things worked but there was no interaction, convenience, or visual layer.

That made me wonder: how could I combine my hardware knowledge with a real user interface?

That question stayed with me.

πŸ“± Step 2: The First Project for Android

I first learned about Android through a university project. We had to build an app that could communicate with a custom device via Bluetooth.

Suddenly, Android made perfect sense. I could connect hardware and users in a modern and intuitive way.

The learning curve was steep.
I had never touched:

But something clicked. Android felt powerful. I could now build apps that:

πŸ’‘ Step 3: Learning Kotlin (and Loving It)

After years of C++, Kotlin felt like a dream.

Features like:

...all felt like a breath of fresh air.

Kotlin made Android development not just possible but enjoyable.
I could finally focus on what I wanted to build, instead of fighting the language.

For someone who spent years doing pointer math that was huge.

🎨 Step 4: Confronting the UI Beast

The hardest part? UI.

I was used to tiny LCDs, buttons, or just serial output not Material Design, gestures, or navigation graphs.

Then I discovered Jetpack Compose.

Writing UI declaratively, in pure Kotlin, just clicked.
I could structure UI the way I would structure logic and that finally made Android UI development click.

🌐 Step 5: Looking at the Ecosystem

Once I got past the basics, I explored more of what Android had to offer.

Things like:

I realized: Android isn't just about pretty apps
you can build real tools, automate workflows, control hardware, and create real-world value.

πŸ€– Why Android Is a Great Fit for Embedded Developers

If you come from an embedded background like I do, Android might feel overwhelming at first β€” but it gives you superpowers:

In many ways, Android is the perfect next step for embedded developers.

πŸ”­ What's Next?

I’ve just scratched the surface and there's so much more I want to explore:

But above all, I want to keep building.

Android gives me the tools. Kotlin gives me the language.
My background gives me a unique mindset.

🧠 In the End

I didn’t plan to become an Android developer but it felt right.
If you're an embedded developer and you're curious, I highly recommend trying out Android and Kotlin.

You might end up building not just devices, but entire experiences.

πŸ“¬ Let's Get in Touch

Are you also moving from embedded systems to mobile development?
Or do you want to explore how to combine hardware with Android?

I'd love to hear your story, answer your questions, or just say hello.

β†’ Get in touch on X. Let's make cool things together.