Skip to main content

Production Playbooks

Architecture guidance explains how a system should be shaped. Playbooks explain how a team should implement and operate the parts that most often fail under production pressure. In React Native, those pressure points are usually authentication, offline behavior, notifications, deep links, feature rollout, and payment-sensitive flows.

Why playbooks matter​

These areas create repeated problems because they cross boundaries:

  • JavaScript and native behavior
  • app code and backend contracts
  • UX and security
  • product goals and operational risk

Without a playbook, each team invents its own solution, and the product slowly accumulates incompatible assumptions.

What belongs in a playbook​

A useful playbook should define:

  • the problem boundary
  • required product and backend contracts
  • mobile architecture expectations
  • observability and analytics requirements
  • failure handling and recovery behavior
  • security or compliance controls
  • team ownership and release concerns

The goal is not to prescribe every line of code. The goal is to prevent costly ambiguity.

Included playbooks​

This section covers:

When to use this section​

Read these pages when:

  • a feature touches login, payments, or stored credentials
  • the app must work under unreliable connectivity
  • user journeys depend on notifications or links from outside the app
  • the team needs safe rollout and kill-switch behavior
  • multiple feature teams are working on the same operational surface

Team rule​

If a product area is important enough to page someone in production, it is important enough to have a playbook.

Use this section alongside Mobile Security, CI/CD and Release Engineering, and Observability and Analytics.