Expo vs Rootly
Side-by-side trajectory, velocity, and editorial themes.
Extending from build-and-ship into runtime observability and CI primitives.
Expo is in active release mode — SDK 55 landed in February, SDK 56 beta is now out, and the team is filling the gaps with build-time wins (Gradle and compiler caches), new product surfaces (Expo Observe in private preview), and developer-ergo additions like GitHub sign-in. A separate thread on Expo Go's App Store posture keeps recurring, signaling continued platform-store friction.
The arc is broadening past "build and ship React Native apps" into the operational layer around them: production observability with Expo Observe, CI primitives via MCP tools and compiler caches, and authentication ergonomics. The SDK cadence remains the metronome, but the most interesting motion is happening adjacent to it — at the dev-experience and runtime-ops edges.
Expo Observe is the directional bet for 2026; expect it to exit preview tying crash, performance, and user-flow analytics directly to the EAS pipeline. On the iOS side, expect ongoing posts and a push toward Dev Client and bare workflows as the more durable distribution path, with Expo Go reserved for prototyping rather than production handoff.
Rootly is moving the incident workflow out of the dashboard and into the IDE.
Rootly is shipping steadily across three lanes: on-call ergonomics (SLA follow-ups, deferred paging, team heartbeats), AI surfaces (Claude Code and Cursor plugins), and enterprise plumbing (Google Workspace directory sync, deeper RBAC). The cadence is roughly one release per week and the changes are coherent rather than scattershot — each lane is building toward a recognizable end-state.
The on-call work is a maturation arc: features that used to be coarse (paging, heartbeats, follow-ups) are gaining ownership, scheduling, and SLA awareness. The AI work is the more interesting axis — pulling on-call context, retros, and incident state into Claude Code and Cursor signals that Rootly wants engineers to interact with the platform inside their editor, not by tabbing away to a separate UI.
Expect the IDE plugins to gain write-side actions next (acking pages, drafting retros, triggering runbooks from the editor), and on-call configuration to keep moving toward team-scoped, RBAC-aware defaults rather than global ones.
See more alternatives to Expo →
See more alternatives to Rootly →