Skip to main content

Command Palette

Search for a command to run...

Expo config plugins in production: the guide that prevents native drift

Updated
1 min readView as Markdown
Expo config plugins in production: the guide that prevents native drift

Every Expo developer meets the config plugin moment eventually. You need a native SDK — push notifications, Sign in with Apple, a Bluetooth library — and the managed workflow suddenly asks you to edit AndroidManifest.xml and Info.plist files that do not exist in your project. That is what config plugins solve: small functions that patch native project files at prebuild time, reproducibly, in version control.

This guide covers how config plugins actually work, the production patterns that keep them maintainable, and the escape hatches for when a library ships without one.


This is an excerpt. Read the full post at otf-kit.dev/blog/expo-config-plugins-production-guide — full-stack kits your AI coding agent can actually ship to production. Browse the kits →

More from this blog

O

OTF — kits your AI coding agent can ship to production

540 posts

Engineering notes on shipping production apps with AI coding tools — Claude Code, Cursor, Codex, Lovable, Bolt — and the stack underneath: React Native, Expo, Next.js, Supabase. Honest takes on what works, what breaks, and the full-stack kits that get you to production faster. By OTF.