FaithGPT Apps: Make Something for Your Church, From a Potluck List to a Bible Quiz
TL;DR: FaithGPT Apps lets you describe a small tool in chat, approve a desktop and a phone mockup, and get a working app that FaithGPT has checked on both screen sizes. The Make something page at /apps/make also covers slides, docs, PDFs, reports and dashboards. A build typically uses about 109 to 284 credits and the price shows before you approve. Free accounts can keep 3 apps; AI-powered apps need Pro or Max to build, and whoever presses Run pays for the run.
Most churches I know run on small tools nobody planned. The nursery rota lives in a spreadsheet one person understands. The potluck lives in a group text that has scrolled past the dish list by Thursday. The greeters write first-time guests on a clipboard, and the clipboard goes in a drawer.
None of that is big enough to justify buying software. All of it costs someone an hour a week. FaithGPT Apps is for that gap, and from today it sits on one page with everything else you can make in FaithGPT.
I spent the last few weeks building real apps with it, the kind I would hand to a volunteer. The screenshots below are those apps, as they run today.
One page for everything you make
Open Apps and the top of the page asks what you want to make: Slides, Docs, PDF, Report, Dashboard or Apps. Each card shows two starting points, and Make something takes you to the full page.
At /apps/make you pick a kind, then either describe what you need or open a template. Every template card has two buttons. Ask FaithGPT to fill it in writes the content from your description. Open the template gives you the template as it is, so you can write it yourself. Pick Apps and you get the app box, a font choice and eight app templates, with the price of a build under the box before you type a word.
Seven apps we built
These are real apps in my account. None of them took more than an afternoon, and most of that afternoon was me deciding what I wanted.
Shared Table, a potluck sign-up. Everyone at church sees one list of dishes, adds what they are bringing and how many it serves, and can see what is still missing. The "What's needed" tab counts mains, sides, desserts and drinks against a target, so nobody brings the fourth pasta salad. Each person can edit only their own entries.
Welcome Desk, a first-time guest log. Greeters record a guest's name, how they heard about the church and whether they asked for a follow-up. You step through Sundays with arrows, and a weekly chart shows how many guests came.
Lesson Lantern, a Sunday school lesson builder. A teacher picks one of ten Bible stories, such as David and Goliath or Zacchaeus, or types any reference, then picks an age group from preschool to older elementary. The app writes a 30 minute lesson in five parts: a welcome activity, the story retold simply, three discussion questions, a craft and a memory verse.
Gather, a small group planner. Type a passage like Philippians 4:4-9, choose how long the group meets, and Gather writes an opening question, discussion questions and a plan that fits the time.
Lampquest Bible Trivia. Pick a book of the Bible and a difficulty, and it writes five fresh multiple choice questions with a running score and a streak.
Ark Pairs and Canon Shelf. Two games with no AI in them at all. Ark Pairs is a memory match where you pair each animal with the chapter its story is in. Canon Shelf is a race to put shuffled books of the Bible back in order. Once built, they cost nothing to play.
Lesson Lantern, Gather and Lampquest use AI, and each one shows the price of a run before it makes the call. More on who pays for that below.
How a build works
You describe the app in the box on the Make page or at Create an app . Then three things happen in order.
FaithGPT writes down what it understood as requirements and draws two mockups, one for desktop and one for a phone. You read them. If the potluck list should show allergy notes, say so and it revises.
You approve the design. Nothing gets built until you do.
FaithGPT builds the app and checks it on a phone-sized screen and a desktop-sized screen before it becomes your working version.
Here are the two mockups Shared Table was built from. They stay in the app's settings, under Design, so you can download them later or compare them with what got built.
I care most about step three. An app that looks fine in one window and breaks on a phone is worse than no app, because the person who finds out is a volunteer standing in a hallway. The checks do not make an app perfect. When they find something small, the app still goes live, and the app page lists what could be better in plain words with a Polish these button that starts the edit for you.
Changing an app later, by asking in chat, gets checked the same way, against the records you have already saved. If that check fails, your working version and your records stay as they were.
Slides, docs and dashboards on the same page
Not everything should be an app. A sermon outline is a document. Sunday attendance is a dashboard. These open in editors made for them.
For slides, Bible verses are filled in from the King James text in the FaithGPT Bible, not written by the AI. I asked for a five slide deck on Psalm 23 and the verse slide came back with Psalms 23:1-3 word for word, with the reference under it. You can present full screen or export to PowerPoint or PDF.
Dashboards take a table of numbers, typed in or pasted from a CSV, and draw charts from it. The numbers on a dashboard come from your table, every time. The AI can suggest which charts to show, but it cannot write a total.
Sharing, remixing and who sees what
New apps start private. You choose who can open one: only you, up to 50 verified email addresses, or everyone with the link. Apps shared with everyone can appear in Community apps once their working version passes its checks.
Each person's records stay in their own account. The person who built your potluck app does not see what you typed, unless the app was set up with a shared list, which is how Shared Table shows everyone the same dishes on purpose. If an app allows it, anyone can Remix it, which gives them their own copy with no records in it. A remix costs no credits. If an app should not be on the list, Report is in its header, and the owner is not told who reported it.
What it costs, and where it stops
I would rather you read the limits here than find them halfway through a build.
Credits. A build typically uses about 109 to 284 credits, depending on its size. FaithGPT holds more than that while it works and releases whatever it does not use, and the phone and desktop checks hold a further amount that is also released if unused. Opening an app, saving records, remixing and sharing never cost credits.
Plan limits. Free accounts can keep 3 apps, 1,000 records and 5 MB of storage. Pro raises that to 25 apps, 25,000 records and 100 MB. Max allows 100 apps, 250,000 records and 1 GB. The Apps page shows the limits on your account, and they can change.
AI-powered apps. Lesson Lantern, Gather and Lampquest send what you type to an AI model. Only Pro and Max accounts can build one. Pro accounts can run AI apps 100 times a day and Max accounts 500. The person who presses Run pays for that run with their own credits, and sees the cost first. The owner of a shared AI app never pays for other people's runs. A Free account can still run someone else's AI app with its own credits, up to 5 runs a day, once its email is verified and the account is a day old.
What stays your job. An app does not know your church. Check that the rota roles match how your team works. Read every trivia question and every lesson before a child sees it. AI makes mistakes, and a shared link carries your name.
Try one
Start with the spreadsheet you dread opening. Go to /apps/make , pick Apps, and describe the tool you wish you had. If you only need a sermon outline or a bulletin, pick Docs or PDF and open a template. The full details on plans, sharing and privacy are in the help article at /help/faithgpt-apps .
Over the next three weeks I will post a walkthrough of a few of these: how Shared Table came together, how the Psalm 23 deck was made, and how we use the games on youth night. Tell me what you build. The best apps I have seen so far were ones I would not have thought of.
Helpful Scripture resources
Contact & support
Email the FaithGPT team at hello@faithgpt.io or visit the contact page .
Explore FaithGPT
