Rafael

Independent developer building thoughtful apps.

Simple tools. Meaningful experiences.

Portrait of Rafael

01 — About

A short version of a long story.

I got hooked on computers early and never really recovered. What started as taking things apart to see how they worked turned into a career, and the fascination survived the transition — which, if you've worked in software long enough, you know is not guaranteed.

Away from the keyboard I'm a husband and a dad. That's the part of my life everything else is arranged around, and it shapes how I build: I have no patience for software that wastes people's time, and I'd rather ship something small and honest than something big and hollow.

Professionally, I've spent my career building software end to end — products, backends, mobile apps, and the infrastructure underneath them. On my own time, I design and release my own apps. This site is where all of it lives together.

The longer version →

02 — Work

What I do, professionally.

My work life is software development — the whole path of it, from a rough idea to a product that's running, monitored, and maintained. These are the territories I work in every day.

  1. /01

    Product engineering

    Taking an idea from "what if" to a real product: scoping what matters, cutting what doesn't, and shipping something people can actually use.

  2. /02

    Backend systems & APIs

    The machinery behind the screen — services, data models, and APIs designed to stay understandable long after the first release.

  3. /03

    Mobile applications

    Designing, building, and releasing apps for Android and iOS — including my own, which live on this site with full support and privacy pages.

  4. /04

    Cloud & infrastructure

    Deploying and running software reliably: cloud infrastructure, automation, and the operational discipline that keeps products alive.

  5. /05

    Data & applied AI

    Data pipelines, integrations, and AI where it genuinely earns its place — used with judgment, not as decoration.

How I work

Three things I hold myself to.

a.

Ship, then improve

An idea that never leaves the editor helps no one. I'd rather release a focused version one and keep refining it than polish something in private forever.

b.

Keep it understandable

Code is read far more than it's written. I build systems the next person — often future me — can open up and reason about without archaeology.

c.

Respect the user

No dark patterns, no attention traps, no data grabs. If I wouldn't want my family using it, I don't build it that way.

04 — Contact

You found me. Say hello.

Whether it's about one of my apps, a professional question, or you just followed a link here and got curious — I read everything that comes in.