Horácio Comé, Android Engineer

~/horacio/portfolio

stable build

site source
androidsince 2018
markets5 shipped
focusnative migration
backendKtor + PostgreSQL

$ whoami

ANDROID ENGINEER

Horácio Comé

I build Kotlin Android apps, native migration work, and backend systems for products that get messy once they meet real users. I care about reliable flows, maintainable code, and staying close enough to the product to solve the actual problem instead of the neat one.

Right now I am focused on Kotlin Android migration work for TrueVUE Cloud and Ktor and PostgreSQL backend development for Markado.

$ ls selected-work/

Selected Work

Android delivery first, with backend ownership as supporting breadth.

truevue-migration.kt

TrueVUE Cloud Migration

view project

role: Android migration lead / current work

androidkotlinnative migrationRAIN RFID

Leading the move from a cross-platform base to Kotlin Android, creating a more maintainable native foundation with better control over device-connected retail workflows.

stack: Kotlin, Android, native architecture, migration strategy

mpesa-multi-market.kt

M-Pesa Multi-Market Android

about M-Pesa

scope: five national markets / around 5 million users

fintechandroid5 marketsreliability

Shipped Android experiences for Mozambique, Lesotho, Tanzania, DRC, and Ghana, where dependable mobile-money flows matter in everyday use, not only at launch.

stack: Android, fintech, multi-market delivery, reliability

kumbase-platform.kt

Kumbase

kumbase.com

role: full-stack product ownership

saaspostgresqlbackupssecurity-first

Built a security-first SaaS for automated PostgreSQL backups, encrypted artifact storage, and portable restore downloads, centered on dependable recovery workflows.

stack: Kotlin, PostgreSQL, backup automation, encrypted storage

markado-backend.kt

Markado Backend

markado.pt

role: backend product development / current work

backendschedulingpaymentsintegrations

Built scheduling, guest, check-in, payment, messaging, and calendar-sync flows that hold together under real operational use.

stack: Ktor, PostgreSQL, Exposed, Stripe, Twilio, SendGrid

$ cat quick-facts.json

At A Glance

  • experienceAndroid engineering since 2018
  • primaryKotlin and native Android
  • mobileKMP, CMP, Android native, Compose, Hilt, Koin, Retrofit, Ktor
  • serverKMP, Ktor, PostgreSQL, Exposed, auth, integrations, background jobs

$ tail -n 4 outcomes.log

Android Track Record

  1. 01Leading a cross-platform-to-native Kotlin migration for a device-connected retail product.
  2. 02Shipped mobile-money Android experiences across five national markets serving around 5 million users.
  3. 03Worked with external-device and RAIN RFID workflows where platform control and reliability matter.
  4. 04Extended Android ownership with Kotlin backend and PostgreSQL product development.

$ cat notes/work-style.md

How I Work

I prefer software that survives real usage and still makes sense later. Usually that means reducing moving parts, staying close to the product problem, and choosing solutions a team can keep operating after the launch energy is gone.