“We need an app” can mean several things. Members may want an easy way to check notices from their phones. Organisers may want bookings, payments or direct messages. A committee may want the community’s name and icon on a home screen.
Write down the job people need to do before choosing an app or commissioning one. The right answer depends on those jobs, not on whether the software comes from an app store.
Turn the request into specific tasks
Ask members to complete the sentence: “I want to open the app so I can…” Their answers might include checking a changed meeting time, finding a document, contacting an organiser or booking a facility.
Separate reading information from carrying out transactions. A searchable information page may handle the first group of tasks well. Bookings, payments, attendance and private messaging need systems designed for those responsibilities.
Understand home-screen access
A web app can be added to a phone’s home screen and, on supported devices and browsers, open in its own window. That can give a community a familiar icon and a direct route back to its information without requiring an app-store download.
Apple documents adding a website as an iPhone web app, and Google explains installing web apps through Chrome on Android. The available options and exact steps depend on the device, browser and website.
A home-screen icon does not by itself tell you which features a service provides. Check separately whether it supports offline access, notifications, bookings or anything else your community needs.
What that means for a PutBoard Board
PutBoard Boards support home-screen access, with a standalone app experience where supported. People can also keep using the ordinary web link. The home-screen launch opens the Board’s home page, giving them a starting point for notices, Events, Information and contacts.
Community and Community Plus support a custom Board icon. The displayed name can be shortened by the device, and the precise appearance varies. Community Plus also offers custom branding and a custom domain. These options help a Board feel familiar to its community without making it a separately built native app.
PutBoard is for finding published information. Do not choose it on the assumption that installing it adds offline reading, push notifications, chat, bookings or payments; those are not features of its current public Board experience.
Choose around the work, including upkeep
- For notices, reference information and dates: test whether a mobile-friendly website or Board already makes the tasks easy.
- For transactions or member administration: look for a service that handles the specific booking, payment or record-keeping workflow.
- For a custom app: identify the capability existing tools cannot provide, and who will fund, maintain and support it over time.
Ask suppliers to demonstrate the tasks with an ordinary member’s access. Include what happens when someone changes phone, cannot install the app or needs help. A polished demonstration by an administrator does not answer those questions.
Try a small information pilot first
Example pilot: give a few members one place to find the next gathering, facility instructions and useful contacts. Ask them to open it through a link, then offer help adding it to their home screens.
A week later, ask them to find the information again. Check whether the familiar icon helped and which tasks still required another tool.
If easy return visits were the main need, that may be enough. If members still need to complete bookings or other transactions, use the pilot to define those requirements clearly. Our guide to noticeboards and community-management software helps separate the responsibilities.