November 10, 2026

PWA vs native app for a resident portal: what each costs

Rodion Salnik

Rodion Salnik

CTO and Co-founder, Brocoders

5 min read

In June 2022, C.I.A. Services, a Texas community association manager in business since 1984, wrote a 25-page spec for an owner, resident, and board app. The spec ruled out native iOS and Android apps, because owners would have to download the app and keep updating it.

PWA vs native app for a resident portal has a short answer: a progressive web app (PWA), which is a website that installs to the home screen and runs like an app. If the portal shows accounts, documents, requests, and notices, build one. We proposed a PWA to C.I.A. Services in 2022 and built Pacholi Monitor as a PWA in 2026.

Native apps from the App Store and Google Play earn their cost when a community needs a store listing or deeper access to the phone's hardware.

TL;DR: A resident portal that shows accounts, documents, requests, and notices fits a PWA. Across 2 agency guides published in 2026, PWAs run from $8,000 to $100,000 or more and native iOS and Android apps run from $40,000 to $250,000 or more. Since iOS 16.4, an installed web app can send push notifications and show badges on iPhone, so iOS is no longer the reason to pay for native.

Table of Contents

PWA vs native app: which format a resident portal needs
What a PWA and native apps cost
How residents install a PWA on iPhone and Android
What changed on iPhone since 2022
What we built for C.I.A. Services and why
The person who pays decides the format
When native is the right call

PWA vs native app: which format a resident portal needs

A resident portal that shows accounts, documents, requests, and notices fits a PWA. A resident opens it from a link and installs it in a few taps, with no store account and nothing to update.

You deploy a change and every resident sees it the same day. Pacholi Monitor, our 2026 PWA for accountants, runs on iOS and Android from 1 codebase (one set of code for both phones).

The decision moves toward native in 2 cases: the community needs a store listing, or the portal needs deeper access to the phone than a browser gives, such as heavy offline or background work.

PWANative app
InstallFrom a link, through the browserFrom the App Store or Google Play
UpdatesLive when you deployStore review on each release, then residents update
iPhone push notificationsYes, from iOS 16.4, once the app is on the Home ScreenYes
Device accessWhat the browser exposesFull
DiscoverabilityA link or a search, no store listingStore search
Codebases12, one for iPhone and one for Android

The case for PWAs in general (offline caching, 1 codebase, instant updates) is in our post on PWA benefits.

What a PWA and native apps cost

In both published agency guides, TekRevol (August 2026) and CMARIX (September 2026), a PWA costs less than native iOS and Android apps. Across the 2 guides, PWAs run from $8,000 to $100,000 or more and native apps run from $40,000 to $250,000 or more.

The ranges overlap, so a large PWA at $100,000 can cost more than a small native build at $40,000. Clutch's app development cost guide (updated September 2026) finds that most projects it reviewed cost $10,000 to $49,999. It adds that building native apps for both iOS and Android "will double the overall price" of 1 native app, and it doesn't price PWAs.

SourcePublishedPWACross-platform (1 codebase for both phones)Native iOS and Android
TekRevolAugust 2026$45,000 to $90,000 (standard custom PWA)$60,000 to $140,000$110,000 to $250,000
CMARIXSeptember 2026$8,000 to $100,000 or moreNot split out$40,000 to $250,000 or more

Both are agencies that sell builds, and these are their ranges, not Brocoders prices. They disagree on the PWA floor: CMARIX starts at $8,000, while TekRevol prices a standard custom PWA at $45,000 to $90,000.

Store fees are small. Apple charges $99 a year for its developer program and Google charges $25 once for a Play account.

In our experience the bigger costs for a portal are the number of codebases, the store review cycle, push notifications, and the integration with the system of record, which holds the official account data.

At C.I.A. Services, the application programming interface (API) that connects the app to RedDog stayed with the C.I.A. Services team. We reviewed it and listed the endpoints (the individual data requests) still missing.

Ask the first quote to price the store apps as a separate line item, so you can add them later.

How residents install a PWA on iPhone and Android

A resident installs a PWA from the portal's own address, with no store account.

iPhone, in Safari

  1. Open the portal address in Safari.
  2. Tap Share.
  3. Tap Add to Home Screen.
  4. On iOS 26 and later, leave Open as Web App on. Earlier versions have no switch.
  5. Tap Add. The icon appears on the Home Screen.

Android, in Chrome

  1. Open the portal address in Chrome.
  2. Tap the More menu at the right of the address bar.
  3. Tap Install and create shortcut.
  4. Tap Install.
  5. Open the app from the home screen or the app drawer.

Design sign-in as a one-time code. On Pacholi Monitor, a sign-in link failed in the installed iPhone app, and the next section explains why.

What changed on iPhone since 2022

iOS is no longer a reason to avoid a PWA. In 2022, web apps on iPhone had no push notifications and no badges. WebKit's iOS 16.4 announcement says a web app added to the Home Screen can ask permission to send push notifications and can show badges.

WebKit's Safari 26 notes say that with iOS 26, every website added to the Home Screen opens as a web app by default. A resident can switch Open as Web App off to keep a plain bookmark.

We saw both sides of that change. When we built the C.I.A. Services app in 2022, iOS showed no badges for web apps, and the client accepted it. In 2026 we built Pacholi Monitor, a tax deadline calendar app for accountants, as an installable PWA.

Web Push (the browser standard for push notifications) works on Android and on iOS 16.4 and later. The release build passed 160 of 160 test cases on iOS and 157 of 157 applicable cases on Android before the July 16, 2026 release.

iOS still has a trap. On Pacholi Monitor, a sign-in link failed in the installed iOS app, because iOS keeps cookies for an installed web app apart from Safari and in-app browsers. Sign-in was redesigned 3 times between May 26 and June 12, 2026, and the owner's first sign-in now uses a one-time code.

What we built for C.I.A. Services and why

The app sits on RedDog NextGen, the management system C.I.A. Services built and relaunched in 2021, which stays the system of record. Before signing, the client asked whether React Native, which builds iOS and Android apps from 1 codebase, could also produce the web app. It also asked whether a non-technical owner would get an icon on the home screen.

The client asked for a web app that works like a mobile app, and we proposed a PWA.

Between July and December 2022 we designed the app and built a React PWA front end against RedDog's API and the company website's endpoints, both written and kept on the C.I.A. Services side.

The person who pays decides the format

The person who runs the app is rarely the person who signs for it. As one Communications and Creative Services Manager at a U.S. residential community put it:

"At the end of the day, they're the bank paying for it."

Price the choice for that reader. Ask for the PWA as the base quote and the store apps as a separate line, so the paying side sees what native would add and can approve the store apps later. Homeowners association (HOA) boards weigh software differently from vendors, as our post on what HOA boards need explains.

When native is the right call

Pay for native apps when a store listing is a requirement, or when the portal needs work a browser can't do, such as heavy offline use or background tasks. A hybrid app wraps web code in a native shell and still goes through the stores.

If you need native apps, ask for them on the same API as the PWA. Our native app development team builds them, including with React Native services when 1 codebase for both phones fits.

If you're scoping a resident or owner portal, we build them as part of our PropTech software development work. See the C.I.A. Services owner app and the other PWAs we built.

FAQ

Is a PWA cheaper than native apps for a resident portal?

In both published agency ranges, yes. TekRevol puts a standard custom PWA at $45,000 to $90,000 against $110,000 to $250,000 for native, and CMARIX gives $8,000 to $100,000 or more against $40,000 to $250,000 or more.

Do PWAs work on iPhone in 2026?

Yes. Since iOS 16.4, a PWA on the Home Screen can send push notifications and show badges. Our Pacholi Monitor PWA passed 160 of 160 iOS test cases before its July 16, 2026 release.

How do residents install a PWA?

On iPhone, open the portal in Safari, tap Share, then Add to Home Screen, then Add. On Android, open it in Chrome, tap the More menu, then Install and create shortcut, then Install. No store account is needed.

Will PWA replace native apps?

No. A PWA covers a portal that shows accounts, documents, and requests. Native apps remain the format when a store listing or deeper device access is a requirement.

Is PWA still relevant in 2026?

Yes. We built C.I.A. Services as a PWA in 2022 and Pacholi Monitor as a PWA in 2026, and iOS 16.4 closed the push and badge gaps that mattered in 2022.

Can residents find a PWA in the App Store?

No. A PWA has no store listing unless someone wraps it or builds native apps, so residents reach it through a link or the community's website. A store listing costs $99 a year for Apple and $25 once for Google.

Read more on our blog