When I first joined the team at me&u, I became part of the mobile team tasked with building Crew.

For a while, I was the only engineer working on Crew. Within the first 4-5 months of joining, I was able to build the app from the ground up and get it into the hands of some early venues for testing.

Once it was live, my team quickly grew as we got a dedicated product manager, designer, and a couple more engineers to help scale the app.

Deployments

When it was just me, I was manually deploying app versions from my machine to TestFlight for the wider company to test. This was fine initially, but it was a slow, error-prone, and quite tedious process. It became clear that this approach wouldn't scale as the team grew.

I ended up implementing a CI/CD pipeline to automate the build and release process as a nightly build, ensuring there's always a build ready with the latest changes to test the next day. The CI/CD pipeline was built using Bitrise.

Testing

To ensure the app's stability and reliability, a comprehensive e2e testing system was implemented using Maestro mobile.dev.

Monitoring

Datadog is used to monitor the app's performance and keep track of any issues that may arise.

Components

To be honest, the initial components were thrown together without much consideration. However, since the team has grown, we have moved to a composition component pattern. This allows for flexibility and scalability as the app grows in both its user base and feature set, but also in the number of team members working on it at the same time.

Styling

Using composition components has allowed us to build a design system that is consistent and easy to maintain. With tokens for colors, typography, and spacing, and components for buttons, inputs, and cards, styling is also made easy.