Sequence · 3 emails over 10 days
Expo sends four emails in a short run, and three of them are onboarding steps that walk a new developer toward their first build. Its subject lines are short and plain, and the onboarding emails name the exact command to run in their content.
Its sequences first, then the emails it sent outside them, in the order they arrived.
Sequence · 3 emails over 10 days
Updated Oct 30, 2026
The first email to arrive, on signup day, is an account verification email with the subject line "Expo email verification" and the preview text "Please verify your email so you can join an organization and access support." It carries a single call to action and asks the new user to verify their email address so they can join an organization and access account support. The email contains no offer, no discount and no product pitch.
That sets the tone for the early messages. The verification email asks the developer to complete a concrete account step rather than making a promotional pitch.
Three of the four emails are onboarding, and each one is part of the Expo onboarding sequence. The first of them arrives on day 3 with the subject line "Create your first build (in 5 minutes)" and the preview text "Run eas build and you're done". The email guides the reader through creating a first iOS or Android build with EAS CLI, provides terminal commands and links to more details.
The next onboarding email, on day 6, has the subject line "Successful developers build early" and the preview text "Developers who build early catch issues before they become blockers". Its content encourages building an app within the first two weeks to catch device-specific issues early, and it provides EAS CLI commands and a link for more detail. The last one, on day 10, is "Ready to test on real devices?" with the preview text "Create your TestFlight-ready build in one command". Its content explains the available build types, gives commands to create a production build and closes with steps for testing on TestFlight and Google Play.
Across these three, the subject lines are short phrases that name a task, and the preview texts for the first and last emails point to a single command. The sequence moves a developer from a first build toward real-device testing.
The most common kind of email in this set is onboarding, which makes up 75% of the emails, with account verification making up the rest. The median send day after signup is day 5, and one email, the verification message, arrives on day 0. The onboarding emails are sent on days 3, 6 and 10 rather than in a burst.
Subject lines are short. The median length is 32 characters. The verification email and the first onboarding email each use a single call to action, and the first and second onboarding emails are plain text.
How often, when and how Expo emails its subscribers, measured from every email we received.
Every email Expo sent in its first month, grouped by the day it arrived.
Day 0
Signup day
Day 3
3 days later
Day 6
3 days later
Day 10
4 days later
Every subject line and preview text, in the order they arrived.