Automating mobile applications from dev to production
summary
React Native apps move from local builds to scripted production deploys using Fastlane + CircleCI with an explicit beta pipeline that uploads to Crashlytics then Google Play beta and TestFlight, after a Cricut release crash caused by version mismatches. Local developer UX improves with NPM scripts for env switching, dev-only debug buttons and a custom Redux middleware for action-to-action performance metrics. CI rejects PRs without tests, Storybook speeds UI work, and the next steps are automated tagging and semantic versioning driven by conventional commits.
AI-written summary · about
chapters (33)
- 0:00Introduction
- 1:27Automation
- 2:20Learnings
- 4:24Culture of automation
- 5:05Buyin from developers
- 6:00Buyin from peers
- 7:10Failures
- 9:12Priorities
- 10:00Refactoring
- 11:38Documentation
- 12:49Talk to teammates
- 13:25Long term speed
- 13:43Ease of accessibility
- 15:03Consistency
- 16:00Sharing knowledge
- 16:52Testing
- 17:50Evolving
- 19:14Play to your strengths
- 20:55NPM scripts
- 22:30Required tests
- 24:12Languages
- 24:55Experience
- 25:56Workflow
- 26:45React Native
- 28:00Redux Middle Way
- 29:11Dev Buttons
- 29:51Fastlane
- 31:34ReactNative
- 34:23Pipeline
- 35:42Fast Lane
- 36:35Semantic Versioning
- 38:09Commits
- 39:17QA to production
related talks
24mAutomate your React Native world with fastlane
27mCICD for React Native
38mThe Power Of Process Automation
35mWeb-Like Development and Release Agility for React Native
27mPractical CI/CD for React Native
26mContinuous Everything in Mobile
46mAutomatic Deployment of iOS and/or Android Apps
31mFrom Zero to DevOps