Expo

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The default-project command selects SDK 57, but the setup path sends learners to store Expo Go, documented as SDK 54. The three Get Started pages give a complete create-start-open path, but the physical-iPhone branch of the environment page demands a paid Apple Developer Program membership while the troubleshooting page says sign.expo.dev needs none, and the default template is SDK 57 while store Expo Go is SDK 54. Three sequential pages (create a project, set up environment, start developing) give an unambiguous path from zero to running on device or simulator.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The pricing Markdown lists every requested quota and overage rate, while the billing FAQ defines reset dates without conflicting values. No page under docs.expo.dev states per-plan MAU, bandwidth, storage, or concurrency counts; the numbers exist only on the marketing site at expo.dev/pricing and its pricing.md mirror. One panelist read the two Production examples as conflicting build credits of $55 and $225. The page figures also fit one $225 credit, with 25 builds using $55 of it. Build credits, MAUs, bandwidth, and overage rates exist in the billing docs but storage limits per plan, exact concurrency, and Enterprise details are absent; the plans page defers all exact numbers to the external marketing site at expo.dev/pricing.

PASS consensus from 3 PASS.

The page gives platform-specific installation, restart, diagnosis, upgrade, and development-build options. A dedicated page matches the exact error string, explains the one-SDK-per-Expo-Go-build cause, branches the fix by iPhone, Android device, emulator, and simulator, and adds package.json, sdkVersion, expo-doctor, and expo install --fix follow-up checks. A dedicated page explains the error, its cause, and gives per-platform recovery instructions for every device type plus an upgrade path.

PASS consensus from 3 PASS.

The webhook page documents creation, POST reception, retries, raw-text handling, and safe signature comparison. One page covers eas webhook:create with its --event, --url, and --secret flags, the 16-character secret minimum, retry behavior outside HTTP 200-399, a runnable Express verification server, an ngrok tip for local receipt, and full build and submit payload examples; the prose omits the sha1= prefix that the sample code compares against. The webhooks page documents creation, payload structure, the expo-signature header format, and provides a complete Express server that performs HMAC-SHA1 verification with timing-safe comparison.

PASS consensus from 3 PASS.

The page's example displays modelName, and the API reference defines osName and osVersion as string | null. The SDK reference gives the npx expo install expo-device command, the namespace import, a working render example using Device.modelName, and declares Device.modelName, Device.osName, and Device.osVersion as string | null with per-platform sample values. Installation command, import path, TypeScript usage example, and full API reference for all constants and methods are on a single page.