The phone side of a portal
Customer Portal Mobile App: Count the Logins Before the Screens
How often will your customer log in? A homeowner with one roof job will do it twice, ever. A monthly client may do it twelve times a year. That single number, more than any feature list, tells you whether a customer portal belongs in a browser or in an app on the phone.
November 18, 2026 · 11 min read
The short answer
For most small businesses, a customer portal should be a mobile-friendly website, because customers who log in a few times a year will not install an app. Save it to the Home Screen when logins become regular. A store app, from $3,750, fits only frequent use with features the browser cannot deliver, and Apple then adds account deletion and demo login requirements.
On this page
- Sort your customers by how often they would log in
- What actually changes when the portal lives on a phone
- The browser portal, saved to the Home Screen
- Rules App Review applies to any app with a login
- Screens, records, and where each one really lives
- The Friday afternoon a customer cannot log in
- Rent the portal when your software already includes one
Sort your customers by how often they would log in
A portal is a door with a lock. Customers go through it to see something you already have: a status, a document, an invoice, a photo. Before deciding what kind of door, work out how often anyone will use it. Pull the last 20 customers, and write down how many times each needed something from you that a portal could have given them. This takes an hour and one cup of coffee, and it will save you a four-figure mistake.
| Example, invented for this table | What to build | Why | |
|---|---|---|---|
| Once or twice per job | A roofer's homeowner checks photos and pays the final invoice | No login at all: a private link in an email or text | Nobody remembers a password for a roof they buy once |
| Every month or so | A bookkeeper's client uploads statements and reads a report | A browser portal with a login, from $575, depending on complexity | Works on a phone and a laptop, and the laptop is where those documents live |
| Every week | A pool service customer checks the visit report and photos | That same portal, saved to the Home Screen | An icon and notifications, with no store and no download friction |
| Several times a week, on the move | A property manager's maintenance requests with photos from a job site | A web app first. Then a store app, from $3,750, if the phone features prove necessary | Camera, offline work and fast sign-in begin to matter, and the user is paid to care |
Our customer portals page covers who logs in, what they see and how it replaces phone tag. This page is only about the phone: what changes there, what Apple asks for, and when the browser stops being enough. The honest headline is that it rarely does. A phone call that says "it is in your portal" is only better than a phone call if the customer can get in.
What actually changes when the portal lives on a phone
Signing in is the whole battle
Passwords on a phone are misery. A link sent to the customer's email or a one-time code removes most of the support calls you were trying to escape. Decide this first, because every other screen sits behind it.
One column, one job
Open on the answer: job status, next visit, balance due. A desktop dashboard shrunk to five inches is a small, unreadable insult.
Documents are the hard part
A 14-page PDF is unreadable on a phone. Put the three facts on the screen, with the full document one tap away. And test uploading from the photo library on a real, older phone.
Paying from the couch
A pay button next to the balance, with a card form from the payment company. See the App Store note below, and adding Stripe for the PCI side.
Being told something changed
This is the feature that drives most requests for an app. An email covers most of it. A push notification needs an app or a Home Screen web app. Text is a separate matter, with its own rules.
The customer's phone is not your phone
Old iPhones, cracked Androids, thumbs in work gloves, and the 16% of U.S. adults who have a smartphone but no home broadband, per Pew Research Center's October 19, 2026 fact sheet. Test on the worst phone you can borrow.

The browser portal, saved to the Home Screen
There is a middle option most sellers will not mention, because it does not sell as well. A web app can be installed. According to MDN, read November 6, 2026, a web app needs a manifest and a secure origin to be installable, and on iOS 16.4 and later it can be installed from the Share menu in Safari, Chrome, Edge, Firefox and Orion. The result sits on the Home Screen beside the banking app. It has an icon and no address bar. Nobody had to approve it.
It also gets notifications. WebKit's February 16, 2023 post says iOS and iPadOS 16.4 added Web Push for Home Screen web apps, provided the site has been added to the Home Screen, has a manifest set to standalone or fullscreen and asks permission in response to a direct user action. So an install-and-allow step comes first. And here is the catch: MDN says the automatic install prompt is not supported on iOS. You have to show people how. A two-screenshot page, or thirty seconds in person at the end of the job, does the trick for the customers most likely to care.
The native versus web comparison has the full decision table. For a portal specifically, what tips it toward a store app is reliable offline work, heavy camera use and customers who will search for you in the store. What does not tip it: wanting your logo on a phone. A saved web app does that already, at a fraction of the price, and any change you make is live for everyone the moment you make it.
A portal nobody can log into is a phone call with extra steps.
Rules App Review applies to any app with a login
A store app with customer accounts takes on obligations a website does not. These come from Apple's App Store Review Guidelines, read November 6, 2026. None is hard. All of them are things somebody has to do and maintain, and none shows up in a cheap quote. We do not, and cannot, promise App Store approval.
- A demo account, with the backend on. Guideline 2.1(a) asks you to include demo account information if the app has a login. That means a fake customer with realistic data, kept working for every update.
- Account deletion, if accounts can be created in the app. Guideline 5.1.1(v) says an app that supports account creation must also offer account deletion within the app. Decide what that does to invoices and job records you still need to keep, and take that part to your attorney or accountant.
- A login only if it means something. The same guideline says an app without significant account-based features should work without one. A portal passes. A brochure with a login does not.
- More than a wrapped website. Guideline 4.2 expects features, content and interface beyond a repackaged website. A portal that is your site in a frame invites rejection. See turning a website into an app.
- Card entry, not in-app purchase, for real-world work. Guideline 3.1.3(e) says goods or services consumed outside the app must use other methods such as Apple Pay or card entry. A repair invoice is not an in-app purchase.
Add the $99 yearly Apple Developer Program fee as of November 2026, which sole proprietors do not get waived, and Google Play's one-time $25 registration. The fees are small. The upkeep is not. For business customers only, Apple's unlisted distribution keeps an app reachable by direct link only, though it still passes App Review, and anyone with the link can open it, so the login carries the weight.
Screens, records, and where each one really lives
Here is a working list for a very small service company, whichever form it takes. Read it as a scope to argue with. The point of the third column is that a portal should rarely own data. It shows what your other systems already hold, and the record of truth stays in one place.
| What the customer sees | Where the data comes from | |
|---|---|---|
| Home | Status of the current job, next visit, balance due | Your job system or a simple table the owner updates |
| Job detail | Photos, notes the owner chose to share, who is coming | Job system, with a "visible to customer" switch on each note |
| Documents | Estimates, signed agreements, warranties | File storage, with access tied to that one customer |
| Pay | Open invoices, a pay button, receipts | Stripe or your processor; invoices sync with QuickBooks through its API |
| Ask | A short message box, and your phone number in plain view | Your email or job system, so nobody opens another inbox |
The dangerous line is the access rule. Customer A must never see customer B's invoice. A mistake there is worse than having no portal, so that check belongs on the server, gets tested deliberately, and gets tested again after every change.
On the card side, Stripe says, read November 6, 2026, that Checkout and Elements qualify for SAQ A, the shorter self-assessment, because the card inputs sit in an iframe served from Stripe's domain. Use one of those. Do not let card numbers touch your own server. In Next.js, per its documentation updated October 5, 2026, pages are Server Components by default, which helps keep API keys off the client. If you handle medical, legal or financial records, take the privacy questions to your own attorney before anything gets built. We are not lawyers, and we build inside your rules.
The Friday afternoon a customer cannot log in
Most portal writing skips this part. It is the part you will live in. Here is how it goes when one person runs the company and the portal, and what has to be true for it to go well.
- 1
The call comes in anyway
A customer says it does not work. You are on a ladder. Your portal has now created the phone tag it was meant to remove, so the sign-in must recover itself: a new emailed link, no passwords to reset by hand.
- 2
You need to see what they see
An owner's view of any customer's screen, from your phone, settles most arguments in a minute. Put it in the first version, and log every use.
- 3
The email address has changed
A new employee, a divorce, a typo. You need a way to change the login address, and a way to check the caller really is the customer before you do.
- 4
The real fix goes to someone else
A bug is not your Friday. Before you launch, know who fixes it, how you reach them and what that costs. Hosting and maintenance start at $55 a month, and the same logic applies to keeping any small site alive.
Rent the portal when your software already includes one
Check what you already pay for. Jobber's pricing page, read November 6, 2026, describes Client hub as a self-serve online experience for approving quotes and paying invoices. Which plans include what is worth confirming before you buy, but a one-truck shop on that platform may have most of a portal already, at $29 a month for Core billed annually as of November 2026. ServiceTitan shops have their own version, and we cover what its portal does and does not do. See the field service page for why renting usually beats writing.
Our prices are public: a web app or customer portal added to an existing site starts at $575, depending on complexity; an iOS or Android app from $3,750. Web application financing and app financing run at 0% with 25% down, up to 12 months. There is no separate small-business rate. We would normally steer a company with fewer than 10 employees to the web version first, and only then decide about the stores, using what a limited-budget app plan recommends. DataCram built and runs its own software, including Athena CMS, so these opinions come with having answered the bug reports. The microbusiness section covers the related ground, and (210) 346-0848 reaches a person.
Questions owner-operators ask
No. A well-built portal is a website with a login, so it opens in any phone's browser with nothing to install. Customers who log in often can save it to the Home Screen. On iOS 16.4 and later that works from the Share menu, per MDN. Only frequent use with demanding phone features usually justifies a store app.
The usual approach is a link emailed to them or a one-time code. It removes the forgotten password calls, which are the first thing a small business notices after launch. The tradeoff is that their email becomes the key, so changing it needs a careful step. Keep a phone number visible for the customer who cannot get in.
If your app supports account creation, guideline 5.1.1(v), read November 6, 2026, says you must also offer account deletion within the app. If you also need to keep invoices or job records, work out what deletion does to them before submission, with your attorney or accountant, since we are not lawyers. Accounts created only outside the app raise a different question to check.
Yes, by email for everyone, or by push if they add your web app to the Home Screen. WebKit says iOS and iPadOS 16.4 added Web Push for Home Screen web apps with permission asked through a direct user action. Texts are possible too, but software-sent texts from a 10-digit number require registration and consent, so factor that in.
A browser portal added to an existing site starts at $575, depending on complexity. An iOS or Android app starts at $3,750, depending on scope, plus Apple's $99 a year or Google's $25 once, as of November 2026. Budget upkeep too. Financing runs at 0%, with 25% down, up to 12 months. Have someone price the smallest useful version first.
For low-risk things like job photos and a final invoice, a long, unguessable link that expires is a reasonable tradeoff, and far easier than an account. Anyone who gets the link can open it, so keep sensitive documents behind a real login. If you handle health, legal or financial records, ask your own attorney what your obligations are first.
Keep reading
- Fewer where-is-my-job callsCustom Customer Portals for Small Businesses: Who Logs In, What They See, What the Phone Stops DoingHow to build a customer portal for a very small business: count the status calls, set the access rules, start with three answers and skip it if you can.
- Two stores, one budgetMobile App Development for Small Business: iPhone, Android or a Web App FirstiPhone and Android apps for a small business: web app from $575, native from $3,750, Google Play and Apple fees as of 2026, and what to build first.
- Two ways to fail, comparedNative iOS App or Web App: A Decision Table for a Business With No IT DepartmentNative iOS app vs web app for a small business: a decision table with real costs, what iPhones let web apps do, push rules, and when native pays off.
- One owner, one phoneWeb Design for One-Person Businesses: What You Need and What to RefuseWebsite design for one-person businesses: the short page list, what to refuse to pay for, and fixed prices from $1,500, or when a builder plan is better.
- The build sideSmall Business Website Development: Who Holds the Keys When the Builder LeavesWebsite development for independent contractors: who owns the code, domain and accounts, what custom means at $1,500, and what you must maintain yourself.
- Probably not. Sometimes yes.iOS App Development for Small Businesses: When an iPhone App Earns Its KeepWhen an iPhone app makes sense for a very small company, what from $3,750 buys, Apple's fees and rules as of 2026, and what to try before you build.
- Everything in MicrobusinessSee the section
From the Insights desk
- GoDaddy Hired Walton Goggins to Sell You a Website. The White Lotus Already Showed You How That Ends.GoDaddy put The White Lotus star Walton Goggins in front of Airo, its 'type a sentence, get a website' AI builder. But a builder hands you a beautiful front desk and nothing working behind it. Why a DIY AI site won't get you found, convert, or compete — and what actually does.
- Headless vs. Traditional CMS for E-Commerce: Which Shape Is Your Store?Headless separates the storefront from the commerce engine. That buys front-end freedom, potential speed and many sales channels — and moves search, SEO, checkout and maintenance onto your plate. Who should go headless, who should stay themed, and the middle path that is usually right.
Tell us what customers keep calling to ask
List the three questions you answer over and over. A person at DataCram replies and says whether that takes a private link, a browser portal or an app, with the price.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.