About Andrés Garrido

Senior Android engineering without the handoff.

Android App Hero is a narrowly scoped service for product teams that need one important Android issue investigated and resolved without adding permanent headcount or opening an indefinite consulting engagement.

AG

Andrés Garrido

Senior Android Engineer

Professional Android work
Since 2013
Engagement model
Direct, fixed-scope B2B
Location
Chile · Remote worldwide

What clients are buying

Focused ownership of a difficult Android problem.

I have spent my career working on Android applications where reliability, lifecycle behavior, integrations, performance, and maintainability matter. Android App Hero packages that experience into a clear commercial decision: one approved issue, one fixed fee, one delivery window, and one senior engineer accountable for the result.

The service is not intended to replace an internal team. It is useful when an issue repeatedly loses priority to roadmap work, requires concentrated Android expertise, or has already consumed more investigation time than the team can justify.

How I work

Evidence before assumptions

I start with reproduction, logs, traces, lifecycle observations, and existing code paths—not a preferred rewrite.

Smallest responsible change

The goal is a reviewable resolution that fits the repository, not a broad architecture project disguised as a bug fix.

Clear boundaries

Acceptance criteria, dependencies, exclusions, required access, and commercial terms are agreed before the sprint begins.

Useful handoff

The delivery includes the root cause, implementation rationale, validation steps, and adjacent findings worth keeping.

Selected technical experience

My Android work has included Kotlin and Java, Jetpack, XML and ViewBinding, Compose, RxJava, coroutines, Hilt and Dagger, Retrofit and OkHttp, Room, Navigation, WorkManager, Firebase, Google Maps, Mapbox, Media3, Salesforce SDK integrations, Gradle and AGP migrations, profiling, LeakCanary, testing, and Clean Architecture.

What the public GitHub profile proves—and what it does not

The public repositories are worth linking because they establish a long-running Android footprint and show work across reusable UI components, architecture exercises, WebRTC, printing, and Android integrations. They should be treated as supporting evidence rather than the main sales proof: several repositories are demos, challenges, forks, or older work and do not represent the scale of confidential production systems.

Have one Android issue that deserves focused attention?

Send enough context for a fit decision. No payment or repository access is required to start the conversation.

Request a fit assessment