Dev Account Wizard
Sign in
Built for church admins

Getting your church app
live is complicated.
We make it not.

Apple and Google require developer accounts before Subsplash can publish your app. Setting them up involves dozens of steps, waiting periods, government IDs, JSON files, and enough technical jargon to derail anyone. We guide you through every single one.

What you're actually signing up for

Here's what Apple and Google
actually require.

This is the honest picture. It's not overwhelming if you have a guide โ€” but it's more than "just create an account."

๐ŸŽ
Apple Developer โ€” 7 steps
1Create an organizational Apple ID on your church's domain email
2Submit enrollment โ€” choose entity type, DUNS, org details, request fee waiver (nonprofits = $0) or pay $99/year (for-profits), verify email with 10-min code
3Wait for Apple review (1โ€“3 days)wait
4Grab Team ID and Team Name from Apple's Membership page
5Enter Apple credentials into Subsplash Dashboard, copy your unique submit email
6Accept the right App Store agreements (and skip the wrong one)
7Invite Subsplash as Admin with the exact right permissions
๐Ÿค–
Google Play โ€” 7 steps
1Set up a permanent org Google account โ€” not personal Gmail, must be on your church domain
2Sign up for Play Console as Organization, pay $25, link Google Payments, enter DUNS
3Upload org document + personal government ID (JPEG only!) for identity verification
4Wait for Google review (1โ€“3 days)wait
5Verify your church website with a Google meta tag
6Invite Subsplash as Admin in Play Console
7Create a Google Cloud service account, generate a JSON key, upload to Subsplash Dashboard

Where people get stuck

The traps that cost
hours of your day.

These are the real reasons people call Subsplash support three times before going live. We've built the fix for every one into the wizard.

๐Ÿชค
DUNS name mismatch
Apple rejects you if your legal name doesn't exactly match D&B's record. We tell you what to check before you submit โ€” and how to fix it after.
๐Ÿ“ง
Personal email as Apple ID
Using someone's Gmail ties your developer account to one person. When they leave, it's a painful transfer. We stop this before it starts.
๐Ÿ’ณ
Accepting the wrong agreement
Apple has a Paid Apps Agreement you should never sign. Signing it triggers requirements you can't easily undo. We flag it clearly.
๐Ÿ“ธ
iPhone photo format
Google requires JPEG for ID verification. iPhones shoot HEIC by default. Google silently rejects the upload. We warn you before you try.
๐Ÿ”‘
Lost JSON key
Google's service account JSON key can only be downloaded once. Lose it and you start over. We walk you through saving it correctly the first time.
๐ŸŒ
Wrong Search Console account
If a previous staffer owns your Google Search Console, website verification silently breaks. We tell you what to look for and how to fix it.

The hidden prerequisite

The DUNS number
almost nobody knows about.

Before Apple will let you enroll, they require a DUNS number โ€” a free 9-digit ID issued by Dun & Bradstreet that proves your church is a real organization. Most churches have one and don't know it. Some need to get one. A few have outdated info that will cause Apple to reject them.

๐Ÿ”
You already have one
Many churches have a DUNS number from a bank loan, government grant, or past filing. We help you look it up in under 2 minutes โ€” you just need your legal name and address.
๐Ÿ“
You need to get one
Getting a DUNS number is free and takes about 10 minutes online. D&B usually processes it within a few business days. We walk you through exactly what to fill in so it matches your IRS records.
โš ๏ธ
Your info is outdated
If your church's name, address, or legal status has changed since the DUNS was issued, Apple will reject your enrollment with a cryptic error. We explain what to fix and how to submit a correction to D&B.

The name problem

Your app store name
and your legal name
probably don't match.

Apple and Google require your developer account to match your IRS-registered legal name exactly โ€” things like "First Baptist Church of Atlantis, Inc." But your app store listing needs to say something people will actually recognize, like "Deep Church..." That conflict stops a lot of churches cold.

โš–๏ธ
The problem

Apple requires "Organization" enrollment under your legal entity name. If your legal name is "First Baptist Church of Atlantis, Inc." but your app needs to say "First Baptist Atlantis" โ€” Apple needs proof you have the right to publish under that public name.

Without that proof, Apple may reject your app submission or list you under your full legal name โ€” which looks wrong in the App Store and on your users' phones.

๐Ÿ“„
The solution โ€” built right in

The answer is a DBA (Doing Business As) letter โ€” a document that says "this organization legally operates under this public name." Think of it like a business proving they own a brand before publishing under it.

The wizard checks whether you need one, and if you do, walks you through creating a simple DBA letter on the spot โ€” pre-filled with your organization's legal name, public name, and address. No lawyer required.

The finish line

Getting everything
into Subsplash.

Creating the accounts is only half the job. Subsplash needs specific credentials entered into their dashboard before they can publish your app. This is where most people get lost โ€” they have everything but don't know where it goes.

๐ŸŽ
Apple โ†’ Subsplash
1Enter your Apple ID, DUNS number, Team ID, and Team Name in Settings โ†’ Developer Accounts โ†’ Apple
2Subsplash generates a unique submit email for your account โ€” you'll use it in the next step
3Accept the Free Apps Agreement in App Store Connect (not the Paid Apps one)
4Invite that Subsplash email as Admin with specific permission boxes checked
๐Ÿค–
Google โ†’ Subsplash
1Create a Google Cloud project and a service account with the Android Developer API enabled
2Download the JSON key file โ€” this can only be downloaded once, so save it carefully
3Upload the JSON key in Settings โ†’ Developer Accounts โ†’ Google Play Developer
4Enter your Google account email, project name, and service account email to complete the connection

The wizard walks you through every one of these steps in order โ€” and the Smart Context Window keeps your credentials ready to copy and paste as you go.

What the wizard does

Your co-pilot for
every screen.

You still work in Apple and Google's sites โ€” but you're never alone, never guessing, and never starting over.

๐Ÿงญ
Screen-by-screen instructions
Every Apple and Google screen is accounted for. We tell you what to click, what to enter, and what to skip.
๐Ÿ”
Credential memory
Your DUNS, Team ID, service account email, app key โ€” saved as you go and surfaced right when Apple or Google asks for them.
โฐ
Wait-state reminders
Apple reviews take 1โ€“3 days. Google identity checks too. We email you exactly when to come back and what step you left off on.
โš ๏ธ
Trap warnings built in
Every known failure mode โ€” wrong email, wrong agreement, JPEG vs HEIC, DUNS mismatch โ€” is flagged before you hit it, not after.
๐Ÿ“‹
Subsplash-ready credential vault
When you're done, everything Subsplash needs is in one panel. Copy and paste โ€” you're live.

Pricing

One price. All in.

Worth it the first time you would have called support for an hour.

$97
One-time ยท No subscription
Apple and Google fees are separate, billed directly by them: Apple is free for nonprofits (fee waiver) or $99/year for for-profits; Google is a one-time $25.
โœ“
Full Apple Developer setup โ€” all 7 steps
โœ“
Full Google Play setup โ€” all 7 steps
โœ“
DUNS number guidance + error recovery
โœ“
All trap warnings built in
โœ“
Wait-state email reminders
โœ“
Credential Vault โ€” always accessible
โœ“
Nonprofit fee waiver guidance