Product Collaboration Best Practices
A condensed summary of the 25 most important product collaboration practices for Expo SDK 57 mobile teams - drawn from every page in this section.
//
Search across all documentation pages
A condensed summary of the 25 most important product collaboration practices for Expo SDK 57 mobile teams - drawn from every page in this section.
Demo on real devices in refinement: iOS + Android preview build or sim recording before sprint commit - Product Collaboration Basics.
Figma is a hypothesis: Handoff checklist includes safe areas, keyboard, and non-happy-path states - not only marketing frames.
Engineer in design crit early: Wireframe-stage attendance catches gesture and navigation issues before hi-fi investment.
Feasibility comment per screen: One engineer note on ticket - spike needed, fallback pattern, or clear - Working with Design & Motion.
Safe area is layout: useSafeAreaInsets - never magic paddingTop: 44 copied from web mocks.
Keyboard states in design review: Primary CTA visible with keyboard up on smallest supported phone.
Touch targets ≥48dp: Enforce in design system components - dense Figma does not override HIG/Material - Design Systems Basics.
Platform parity is a decision: Document intentional iOS/Android differences in ADR - Platform Parity Decisions.
Native chrome over custom imitation: System back, share sheet, and pickers unless brand ADR says otherwise.
Gestures flagged before pointing: Swipe, drag, pull-to-refresh tickets link Gesture Handler feasibility - Gesture Handler.
Motion spec before hi-fi lock: Trigger, duration, interrupt, reduced-motion fallback - Animations Basics.
Reanimated for gesture-linked UI: Scroll-linked headers and swipe rows - not Animated with JS-thread scroll - Reanimated 4.
30-minute motion spikes: GO / SIMPLIFY / DEFER verdict with screen recording on mid-tier Android.
Phased delight is valid: v1 static transitions + v1.1 motion - label in roadmap, not hidden descope.
Estimates are ranges: Engineering + discovery + release calendar - Estimation & Risk on Mobile.
OTA vs store on every ticket: JS-only OTA path stated; native changes trigger store timeline honesty.
Store review buffer explicit: +2–5 calendar days on binary releases - never promise users a date at merge.
Native spikes are billable discovery: 0.5–2 days with written outcome - not hidden padding.
Risk register on epics: Top three risks reviewed weekly with PM - likelihood, impact, owner.
Debt in the portfolio board: SDK upgrades and perf beside features with business risk - Prioritizing Tech Debt vs Features.
Crash-free in stakeholder updates: ≥99.5% target with plain-language impact - Stakeholder Communication.
Trade-off memos: Three options, recommendation, decision date - engineering recommends, PM decides.
Yellow flag early: Estimate bust same-day - revised range beats demo-day surprise.
PR screenshots both platforms: Unintentional parity drift is a bug; intentional drift is documented.
Tokens over one-off pixels: Color, spacing, and motion presets in design system - screens compose components, not literals - Theming & Brand Flavors.
Device demo in refinement - one 10-minute walkthrough prevents more rework than any process doc.
Share this best-practices page + OTA Updates Basics - OTA vs store is the most common misconception.
Frame as protecting craft - fewer emergency simplifications post-sprint. 30 minutes at wireframe saves days of hi-fi rework.
When adding gestures, sheets, or OS upgrades (e.g. Android predictive back). Otherwise quarterly audit of screenshot pairs.
Weekly mobile health message - release stage, crash-free, top issue, ask. Incidents get impact-first template same day.
Stack versions: This page was written for React 19.2.3, React Native 0.86.0, and Expo SDK 57 (
expo~57.0.4).
Reviewed by Chris St. John·Last updated Jul 19, 2026