What's possible
Last time: how I'd lead — open testing, a transparent web committee, and a few ideas beyond the website. Read it here.
A rides app that we deserve is the primary reason I'm running, and it's where I'd start the work. But it's not what I'd look to end on. Because tools.nycc.org is built by real engineers from the start, much is possible that the club has never had. Some of it is ready now; the rest is in-reach, with the right leadership.
If it were up to me, I would pivot from app.nycc.org, and use tools.nycc.org for the rides platform.
— Club member and former volunteer on Membership_App/app.nycc.org team · Read the endorsement
First, the one you can use today.
In beta An Android app. It's in beta now, available to any member on request.
The rides feed in the Android app
What's possible:
- Planned Discord linked to membership. Your club membership recognized in Discord automatically, with no email requests or delays
- Planned Direct access to the club's Ride with GPS account. The NYCC route library shows in your RWGPS account w/o needing a bookmark
- Planned Auto-provisioned Discord channels for big rides. A large ride would get its own channel, created when the ride is posted and archived when done
- Planned Ride publication where members already are. Email, Discord, and WhatsApp — opt-in, per member and channel
- Planned Delegated ride approvals. Ride coordinators can hand off approvals during vacations or peak season, so that ride approvals do not stall waiting on one person (and creates a natural path to develop new ride coordinators)
- Planned Train coordination with the transit authorities. Request group train space right from our app - no dual-entry
- Planned A clear view of the member lifecycle. For the club, we can see when members join, drop off, or sign up and never ride — and then decide to do something about it
If one of these matters to you — or you'd like to try the Android app — tell me at scottfornycc.site/help.
Scott