Skip to main content

FAQ

Common questions about the church app program.

Why is my app a different color than the demo screenshots?​

Your app inherits your church's own brand palette from your website design settings. The demo screenshots use sample branding. Different colors mean the system is working correctly — it's pulling your church's colors into the app automatically.

If the colors aren't matching your church's actual brand, check your website's design settings. Updating those will cascade into the app. See Choosing Your Template for more detail.

What does this cost?​

Apple Developer Program: $99/year — but Apple waives this for qualifying nonprofits. Most churches qualify. Request the waiver during enrollment and you may pay nothing annually. See Apple Developer Account Setup.

Google Play: $25 one-time registration fee. No annual renewal.

FaithMade's own app plan fees are separate — check your FaithMade subscription for details.

Do I really need my own developer accounts?​

Yes. Apple's App Review Guideline 4.2.6 requires that template-built apps be submitted under the content provider's account — that's your church, not FaithMade. This isn't a FaithMade policy, it's Apple's rule. The good news is it also means you actually own your listing.

What can FaithMade do in my account?​

With App Manager access (Apple) and Release Manager access (Google), FaithMade can:

  • Submit new versions of your app
  • Respond to technical review issues from Apple or Google
  • Upload builds and manage your app's metadata

FaithMade cannot access your personal financial information, your other apps, or anything outside of your church app.

What can't FaithMade do in my account?​

FaithMade's collaborator access is scoped to your app. We can't:

  • Access billing or payment information on your account
  • Create or delete other apps in your account
  • Change your developer account settings or ownership

You remain in full control of your account.

What happens if we leave FaithMade?​

Your app listing, your ratings, your app identity — all of it stays with your church. You own the developer accounts. You can:

  • Remove FaithMade's access at any time
  • Continue publishing updates yourself or hire someone else to do it
  • Keep your app live on the App Store and Google Play

Nothing gets taken down. Your congregation doesn't lose access. You just manage the app without FaithMade.

Can FaithMade submit the app under their own account instead?​

No — not for the App Store. Apple's policies prohibit it for template-built apps. Google Play is more flexible technically, but the church owning their own Play account is still the right model for the same reasons: you own your listing and aren't dependent on FaithMade's account health.

We already have an Apple Developer account. Do we need a new one?​

No — use the one you have. Just make sure it's enrolled as an Organization (not Individual). Individual accounts can't support the submission workflow FaithMade uses. If your existing account is Individual, you may need to re-enroll.

What if our DUNS number is wrong or doesn't match?​

Contact Dun & Bradstreet directly to correct it. Apple's enrollment process will stall if the name or address on your DUNS doesn't match what you submit. It's worth double-checking the name matches your legal church name exactly before starting Apple enrollment.

How do we know when the app is live?​

You'll receive an email from Apple or Google when your app goes live. FaithMade will also notify you — but check your own developer account too. It's your listing.

Related: Overview · Apple Developer Account Setup · Google Play Setup · Launch Checklist & Timeline · Troubleshooting