I build and lead mobile products that can scale.

Context

High-traffic retail banking where Login, Home, and Plin are gateways to critical flows.

Problem

Refresh brand identity and experience without interrupting operations or breaking sensitive flows.

My role

• Own the technical roadmap for Login, Home, and Plin rebranding.
• Align design, product, and engineering without breaking critical banking flows.

Technical decisions

• Prioritize high-risk modules for controlled migrations.
• Clear contracts between brand design and mobile engineering standards.

Result

Critical flows coordinated without sacrificing operational continuity; brand aligned with engineering standards.

Learnings

In banking, rebranding is a delivery-architecture and risk problem, not only a UI refresh.

Context

Industrial/commercial greenfield that needed shared logic across platforms from day one.

Problem

Ship a functional product quickly without duplicating Android/iOS architecture or sacrificing standards.

My role

• Mobile leadership and technical strategy with Kotlin Multiplatform.
• MVI, Coordinator, and Clean Architecture as squad standards.
• Additional support for La Calera in the same period.

Technical decisions

• KMP to share domain logic and cut duplication.
• MVI + Coordinator for predictable navigation and state.

Result

First functional release in under 3 months; second release on track around month 4.

Learnings

KMP accelerates when squad architecture and contracts are defined before the feature rush.

Context

Industrial product with Quotation, Clients, and Self-build modules plus XML technical debt.

Problem

Modernize UI and production delivery while leading the mobile team.

My role

• Stepped into mobile leadership: standards, code review, and mentoring.
• Progressive Compose migration for Quotation, Clients, and Self-build modules.
• Applied MVI, Coordinator, MVVM, and Clean Architecture.
• CI/CD pipelines for reliable production releases.

Technical decisions

• Incremental XML → Compose migration by business module.
• CI/CD as the enabler for frequent, safe releases.

Result

Critical modules migrated to Compose; production CI/CD and reduced XML technical debt.

Learnings

Compose modernization works best with standards leadership and pipelines, not screen rewrites alone.

Context

High-volume banking app covering payments, digital card, and contactless wallet.

Problem

Deliver sensitive payment and device capabilities with quality and reliable pipelines.

My role

• Automatic payments, Digital Card, and device unlink.
• Contactless wallet payments with Jenkins pipelines.

Technical decisions

• MVVM for high-traffic features.
• Jenkins CI/CD for controlled releases.

Result

Automatic payments, digital card, device unlink, and contactless wallet capabilities shipped to production.

Learnings

In banking, pipeline reliability is part of the product as much as the feature itself.