— How we work

Shipping multiple times a day on a small team.

GitHub Actions runs every check, Fastlane + EAS pushes mobile builds, Firebase Hosting promotes web on green. Secrets stay in Google Secret Manager. The studio prefers small, frequent deploys.

3 min readPublished 2026-05-02By AptixLabs studio
Lines of code on a dark terminal, representing CI/CD pipelinesAptixLabs · 2026-05-02

Every project at AptixLabs lives in GitHub with branch-protection rules and required CI checks. The studio prefers small, frequent deploys over big releases — it ships multiple times a day on active projects.

What CI runs

  • TypeScript type-checking with strict mode
  • ESLint with the project's ruleset
  • Vitest unit tests for the logic layer
  • A production build to catch any runtime config mistakes
  • Firestore security-rule tests via the official Firebase emulator

Web deploys

Marketing sites and the coach portal deploy to Firebase Hosting through a GitHub Actions workflow that promotes the build only after CI passes on the main branch. Preview channels spin up for every PR — a partner can see a working build before merge.

Mobile deploys

The mobile apps deploy through Fastlane and EAS Build to App Store Connect and Google Play. There's a manual gate before release-to-production but automatic uploads to TestFlight and internal-testing tracks. The same commit can ship to web in five minutes and mobile within an hour after store review.

Secrets

Secrets live in Google Secret Manager and are fetched at runtime — never baked into the build. CI uses workload-identity federation rather than long-lived service-account keys.

Have a project like this?

The studio is taking on a small number of partners. Tell us what you're building — we reply within a working day.

Start a conversation