An HOA community app is mostly notices, documents and money it is not allowed to take.

Dues money does not go through the App Store

Apple sorts payments by where the thing being bought is used. Guideline 3.1.3(e) covers goods and services outside of the app. If your app lets people buy physical goods or services that are consumed outside it, those payments must be collected some other way than in-app purchase. The guideline names Apple Pay and ordinary credit card entry as the examples. Assessments pay for landscaping, insurance, the pool pump and the private road. None of that is consumed in the app, so dues sit on that side of the line.

What does need in-app purchase is anything that unlocks a feature inside the app itself. That is guideline 3.1.1: subscriptions, premium content, extra capacity. Almost nothing in a homeowners association app is that. Fines, transfer fees, clubhouse deposits and a replacement gate remote are all real world charges. So the app either hands the resident off to whatever the association already uses, or embeds a card form from a payment provider the association contracts with directly.

Write the money path into your review notes plainly: the owner pays the association for work done on the property, and the association receives it. There is nothing to unlock. A dues screen that reads like a subscription screen invites the wrong question from a reviewer.

Voluntary money behaves differently from assessments and is worth keeping apart in the data. The block party fund, a playground appeal, a collection for the retiring groundskeeper: nobody is in arrears if they skip it, and nobody gets a lien. That is closer to a donation tracking app than to a dues ledger, and mixing the two makes both reports wrong.

Apple App Store Review Guidelines, 3.1.3(e) goods and services outside of the app

Some of what it holds is a legal record

Florida is the clearest example of a state writing this into law. Since 1 January 2025, an association with 100 or more parcels has had to post a defined list of documents. The statute lets that be a website or an application that can be downloaded on a mobile device. The list is specific: articles and bylaws, the declaration, current rules, the annual budget and any proposed budget, financial reports, insurance policies, and notice of any member meeting together with its agenda.

The same subsection sets an access rule that matters more than it looks. The site or app must contain a subpage, portal or other protected electronic location that the general public cannot reach and that only parcel owners and association employees can. So the app has two visibility levels on day one, and the roster with its mailing addresses lives on the protected side. Florida also keeps whole categories out of view even from members, including attorney client material, medical records, gate visit logs and personal identifying information such as licence and card numbers.

Two build consequences follow. Records have a retention floor, seven years in Florida unless the governing documents ask for longer, which makes deletion a policy question rather than a tidy up. And Florida is not everybody: other states set their own notice periods and inspection windows, and your declaration can be stricter than the statute. Read your own association act before deciding which screens are the record of something.

Florida Statutes 720.303, association records, meetings and the website or mobile application requirement

What residents actually open it for

Take the legal duties out and what is left is a short list, used unevenly. An announcement they can find again next week. The gate code and the bin day. A maintenance request with a photo, and some sign that a human saw it. Booking the clubhouse or the tennis court without three emails. A guest parking pass before the in laws arrive. Who to call about a burst sprinkler at nine on a Sunday.

The roster is the quiet core of the thing. Who owns which parcel, who to contact, who is current, who is renting rather than living there. Keeping that honest is the same problem a membership management app has, and it is where homemade tools rot first. An owner sells, nobody updates the app, and the violation notice goes to somebody who moved out in March.

Requests need a state, not a tick. Received, seen, assigned, done, or declined with a reason. A resident who can see that their fence question is with the architectural committee stops sending the third email, and the board stops relitigating decisions it already made. That is the real gap between a community association app and a group chat: the chat has no status and no memory.

The board changes every year and the app has to survive it

The hardest constraint here is not technical. Boards turn over at the annual meeting, and whoever set the app up may not be on it next spring. Anything tied to one person's personal account becomes a problem at the next election: the Apple Developer account, the admin login, the domain, the payment provider. Put them in the association's name, with at least two current officers holding access, and write down where they are.

Roles follow the rules more than taste. Owners see notices, documents and their own account. The board sees requests, violation history and the full roster. A management company sits somewhere in the middle and should be removable without a rebuild, because contracts end. Where you draw the line between board members versus residents decides most of the screens you will build.

Decide early what the app must never show. Per household arrears, legal correspondence, anything an owner told the board in confidence. A neighbourhood HOA app does not need to be big to be useful: two hundred households, five screens, one officer who keeps the roster accurate. It needs to be the place where the answer lives, every time, including after the board that built it has gone.