Member Experience

The Icon Was The Real Question

About forty minutes into most demos, somewhere in the middle of the member portal walkthrough, someone invariably unmutes and asks a very familiar question. "Do you have an app? An Android app?"

It is never a hostile question, of course. It is a practical one. Their members live on their phones, and she wants to know whether we have met them there.

For a long time my answer was that we built the portal to be mobile-first. That it is responsive by nature. That the course calendar renders one way on a desktop and another way on a phone, and that a member with a saved card can pay an invoice with one click from the parking lot outside a listing appointment. All of that is true. None of it ever fully landed, because it was not really what she was asking.

She was not asking about layout. She was asking about the icon.

What a Member Means by "App"

Ask a REALTOR® to define an app and nobody describes a compiled binary distributed through a store. They describe a picture on a home screen they can tap. That is the entire definition. Tap it, the thing opens, it fills the screen, it knows who you are. It can access your phones special capabilities.

Everything else about a native app is overhead. Submission. Review. Approval queues. Separate codebases for iOS and Android that drift apart a little more with every release. And the worst of it: a version sitting on somebody's phone that we cannot reach and cannot fix, quietly telling that member something that stopped being true a long time ago.

So we made the portal a Progressive Web App (PWA) instead.

A member opens the portal on an iPhone or an Android phone and adds it to their home screen. The icon that lands there belongs to the association, not to us. One 512 pixel mark, scaled down cleanly to every size the home screen, the desktop, and the navbar ask for. Tap it and the portal launches standalone. No address bar. No browser chrome. It carries their session, honors their deep links, and puts them where they were going. A service worker caches the app shell, so it opens fast, and when the signal drops in a stairwell it says so plainly instead of handing them a dead white page.

The Part No Member Ever Sees

We release every two weeks, on a Wednesday night. Thursday morning, every member on every phone is running exactly what we shipped. Nobody downloads anything. Nobody ignores an update prompt for weeks. There is no stale version in the wild to support, because there is no stale version.

Our clients get one portal to explain to their members, not three, and one place where every improvement lands at once.

That is not a compromise we settled for. It is the reason we chose this this route.

No store. No gatekeeper. No download. No stale copy of the truth in somebody's pocket.

Text Link