BUILT INTO EVERY GOODSPEED APP
Transactional Email via Resend
Templated emails (welcome, password reset, receipt, trial-ending) are sent via Resend from a shared Edge Function with every send logged to a delivery table, so you have an audit trail and can replay failed sends without duplicating send logic across features.
- Tier: Common
- Status: Config-toggled
- Config: features.transactionalEmail.enabled
WHY IT MATTERS
Most mobile app projects spend weeks plumbing the same infrastructure before writing a single line of product code. Transactional Email via Resend is one of those cross-cutting concerns that every app eventually needs but almost none get right the first time. Permissions are handled incorrectly, tokens expire silently, or the feature breaks after an OS update nobody tested against.
Goodspeed solves this by shipping transactional email via resend as a production-grade, tested implementation inside every generated app. The code follows the patterns in the GAS template - the same 246-feature catalog that powers every app we build. Controlled by `features.transactionalEmail.enabled` in gas.config.ts. You own the code from day one, can read every line, and can hire any React Native developer to extend it. The build pipeline verifies the feature compiles and routes resolve before the app lands in your repository, so you are not the one catching the integration error at 2 am before launch.
HOW IT IS WIRED
Real code from the GAS template
The excerpt below is lifted verbatim from gas.config.ts in the gas-template repository. This is the code your generated app gets, not pseudocode, not a description of intent.
// Enable this feature in gas.config.ts
export const gasConfig = {
features: {
// Set the relevant flag to true to enable
},
};Source: goodspeed-apps/gas-template → gas.config.ts
HONEST LIMITS
When Transactional Email via Resend is the wrong choice
Not a replacement for bulk marketing email. Resend's transactional pricing and rate limits are designed for triggered sends, not newsletter blasts.
Tier: Common · Config-toggled
Evaluate your use case
Check whether transactional email via resend aligns with your target audience, platform constraints, and regulatory environment before enabling it.
Audit the config
The `features.transactionalEmail.enabled` flag controls this feature. Set it to false in gas.config.ts to disable the feature entirely with no residual code paths.
Seek alternatives
If the built-in implementation does not fit, the generated codebase is standard React Native + Expo code. Any library in the Expo ecosystem can replace the default.
APPS USING THIS FEATURE
Every generated Goodspeed app includes transactional email via resend. Browse the ideas catalog to see apps across all categories that ship with this feature wired in.
CAPABILITIES
Transactional Email via Resend capability breakdown
Concrete dimensions of what the built-in transactional email via resend implementation covers. These reflect the actual template code, not a marketing summary.
| Item | Description | Strength |
|---|---|---|
| Storage backend | Data for this feature is managed by Resend API + Supabase Postgres (email_log table). | Resend API + Supabase Postgres (email_log table) |
| Network mode | This feature operates in Online-only mode. | Online-only |
| Sync frequency | Data syncs On-event (triggered per user action). | On-event (triggered per user action) |
| Tier | Common feature — config-toggled. | Common |
| Template status | Enabled via features.transactionalEmail.enabled. | Config-toggled |
GET IT BUILT INTO YOUR APP