Mobile Engineer

Real-Time Data (WebSocket / SSE)

Perché: Lets you ship live prices or chat over WebSocket or SSE that reconnects after a tunnel or app resume and does not drain the battery, instead of a feed that silently goes stale.

Deep Linking & Universal Links

Perché: Lets you make a campaign link open the right screen whether the app is installed or not, and keep attribution intact, which a basic URL scheme cannot do.

Animations & Gestures

Perché: Lets you build interactions like a draggable sheet or swipe-to-dismiss that run on the UI thread without dropped frames, where a naive animated state change would jank.

App Size Optimization

Perché: Lets you cut a binary that is blocking installs on low-storage devices or cellular download limits, using tree shaking, compression and on-demand resources without breaking features.

E2E Testing (Detox / Integration)

Perché: Lets you keep a Detox or Maestro suite stable on device farms and quarantine flaky tests, so a red build means a real regression and the team still trusts the signal.

CI/CD for Mobile (Fastlane / EAS)

Perché: Lets you automate signing, builds and beta distribution with Fastlane or EAS, so a release train runs on schedule instead of depending on one person's laptop and certificates.

Monorepo for Mobile

Perché: Lets you split shared packages from app code so several teams change one codebase without breaking each other's builds or slowing every CI run.

Feature Flag & A/B Testing

Perché: Lets you roll out a risky change to a slice of users behind a remote flag and read its effect on retention or crashes, since store review makes a bad release slow to reverse.