Design an App Home Screen People Actually Use

Two screens, two jobs

A church website and a church app answer different questions, and confusing them is the most common reason app home screens end up cluttered and unused.

The website is for people who are not yet part of your church. It answers "should I come?" The app is for people who already have — it answers "what do I need from my church this week?" Same organization, entirely different visitor.

This module is about building the second one well: what earns a place on the home screen, how to order it, and how to publish changes without breaking things for the congregation.

Earn the tile

Every item on a home screen competes with every other item. The test for inclusion is simple: does a regular attender need this often enough to look for it on their phone?

Things that usually pass: giving, this week's events, groups, the current sermon or devotional content, prayer. Things that usually fail: the church's history, the full staff directory, a doctrinal statement, last year's annual report. None of those are unimportant — they just belong on the website, where someone can find them the once or twice they actually need them.

A useful discipline: cap the home screen at what fits on one phone screen without scrolling. If something new deserves a place, something existing has to lose one. That constraint forces the prioritizing that otherwise never happens.

Order by frequency, not by importance

Church leaders naturally order things by theological importance. Congregations use them in order of practical frequency. These are not the same list, and the app should follow the second.

Giving may not be the most important thing your church does, but it is one of the most frequently sought — so it goes near the top. Your statement of faith may be far more important, and belongs on the website, because someone reads it once.

Seasonal reordering is worth doing and rarely done. During Advent or a building campaign, the thing everyone is asking about should move up, then move back down afterward. A home screen is not a monument.

Publish without fear

The reason volunteers avoid editing an app home screen is that it feels irreversible and public. The fix is to work in a way where it isn't either.

Make changes as a draft, look at the preview on an actual phone rather than a desktop browser, and only then publish. Where a platform offers a shareable preview link, use it to get a second pair of eyes before the congregation sees anything.

Then know how to undo. Version history and a rollback turn a scary edit into a reversible one, which in practice is what determines whether a nervous volunteer is willing to touch it at all. Before your first real edit, find out whether your platform has this — and if it does, practise reverting once on something trivial so you know the path when it matters.

How the tools differ here

Website builders with an app add-on. Generally shallow: the app is a wrapper around the site, and there is often no separate home screen to design at all.

Custom-built apps. Full control, real development cost, and every change goes through whoever built it — which in practice means changes stop happening.

Church platforms with a configurable home screen. Breeze, Subsplash, Tithe.ly, and Faith Software's own myChelper take this approach, with tiles an admin can arrange, a draft-and-preview step before publishing, and version history to revert a change. The features to compare are whether you can preview before publishing and whether you can undo — those two matter more day to day than how many tile styles are on offer.

Your exercise

List everything currently on your church's app home screen — or everything you're planning to put there. Beside each, write how often a regular attender would genuinely need it: weekly, monthly, once a year, or never. Move anything below "monthly" to the website.

Then open the result on a phone, not a laptop. Home screens designed on a wide monitor almost always turn out to be one or two tiles too many.