If you want an app for your club, could one busy organiser make it and keep it useful? That is a practical test of Glassly. The workflow below is an example to try, not a report of a customer launch or a measured build time.
Choose one job for the app
For this example, the job is simple: members can find the next run, see where to meet and RSVP. Start with the community hub template, which includes announcements, events, groups and member features. It is a premium template, so it costs credits to claim; if RSVPs are all you need, the free events template covers them. Read its limits first: it does not collect dues or membership fees.
Set it up as the organiser
Create the template (the club's own name goes on with any plan), then make an account inside the app. Appoint that account through Who runs it in Glassly's settings. Add a sample event with a meeting point and time. Keep sample details separate from the information members will rely on for a real run.
Test it as a member
Use a second account to find the event and RSVP. Check the member cannot edit organiser content. Change the meeting point as the organiser and confirm the member sees the update. If notifications matter to your club, configure and test them on a phone, including when the app is closed; a live change in an open preview does not prove push delivery.
Try the install before inviting the club
For iPhone installs through Glassly, connect your own Apple developer account (standard fee $99/year, paid to Apple). Android installs from a link, subject to device permissions and developer verification. Publishing on Google Play needs your own developer account ($25 once, paid to Google). Start with a few consenting testers on the platforms your members use. Follow the installation guide and check the app opens, signs in and saves an RSVP on each device. The install link is a distribution method, not a restriction on who can sign up.
Decide whether it earns a place in the week
Ask testers to find the next run without help. Record where they get stuck and whether the organiser can keep the information current. These observations tell you more than the presence of an icon on a home screen. Keep the existing group chat if it still serves the club; the app only needs to make the event information easier to find.
The community hub costs credits to claim and the events template is free. Requested changes use credits, and a production app needs your own Supabase project. See costs and hosting limits and the full workflow before inviting the whole club.