WedMeGood Android delivery foundations

Android Engineer20229 months4 people2 min read

Improved the Android team’s delivery loop with 60% faster local builds, GitHub Actions CI/CD, and a shipped feature revamp.

Overview

At WedMeGood, I focused on Android delivery quality: faster local feedback, less manual release work, and a production feature revamp that benefited from those foundations.

Problem

The team needed to move faster without treating platform work as a separate track from product delivery.

Constraints

  • The team needed immediate day-to-day build improvements, not only long-term cleanup.
  • CI/CD had to fit existing repository habits without adding ceremony.
  • Feature delivery had to continue while engineering foundations improved.

Approach

I optimized Gradle configuration, introduced GitHub Actions based CI/CD, and owned the Wedsta Family Makeup module revamp so platform improvements showed up in real product delivery.

Key decisions

Prioritize build-time wins before introducing more process

Reasoning

The team felt the pain locally every day. Improving the inner loop first made the delivery work immediately useful.

Alternatives considered
  • Start with release automation only
  • Defer build optimization until after feature delivery

Use GitHub Actions for CI/CD

Reasoning

It fit the existing workflow and introduced release automation without extra operational overhead.

Alternatives considered
  • Continue mostly manual release steps

Tech stack

  • Kotlin
  • Gradle
  • GitHub Actions
  • CI/CD
  • Android

Result and impact

  • 60% reduction
    Local build time
  • CI/CD introduced for Android
    Delivery maturity
  • Led revamp and release of Wedsta Family Makeup
    Feature ownership

The team gained a faster development loop and a more reliable release path while continuing to ship user-facing Android work.

Learnings

  • Developer experience improvements are often the fastest path to better team output.
  • Lightweight automation can create outsized impact in growing product teams.
  • Platform work builds trust when it ships alongside visible product outcomes.

This project mattered because it changed how quickly the team could move, not just what one feature looked like in production.

All projects