Release 28 - Problems and Solutions
Release 28
Release 28 is a more technical write-up than usual. Each change starts with the problem that prompted it and follows with how lookingforgroup.social solves it.
Upcoming events in your email
Problem: Members forget events between the day one is published and the day it happens and Club managers have no easy way to nudge members who have not answered. It feels bad to have a scheduled event that people said they were coming to but forgot to put it on their calendar or forgot!
Solution: The daily notifications email and the weekly updates email both gain an "Upcoming Events" section. The daily email lists tomorrow's events as a reminder, and the weekly email lists the next seven days as a look-ahead. Each entry give a direct link to the event to RSVP and the hosting club. If a user RSVPs in the negative they do not receive any messages as we don't want to pester anyone that already said they are not coming.
Upcoming events on the dashboard
Problem: To see what events are coming up, a user had to open each club's Events tab or dig through old notifications. The emails list upcoming events, but the dashboard did not.
Solution: Getting people organized and social is the primary goal of the lookingforgroup.social website! The dashboard has a new Upcoming Events card on the dashboard for easy access to events. It lists the events of clubs you belong to, in any RSVP status (including not answered), nearest first. Events appear up to 30 days ahead and stay listed until 4 hours after they start, so someone running late can still find the address.
An RSVP a user makes in the app updates the entry immediately in the dashboard. Choosing 'Not attending' hides the event in the card while keeping it available on the club's event page if a user changes their mind.
Internationalization Considerations
Dates are formatted with localized formatting, so French readers get their expected date formats and language. Why did lookingforgroup.social choose French for a mostly American audience? Well, the lead developer can read French and do a rough check for translations. The primary concern is to bake-in i18n from the beginning because it is really hard to do after the fact.
Operators see open feedback every day
Problem: User feedback could sit unnoticed until an Operator thought to run a command to list it. There is a daily Operator summary email already reporting requested pending verifications, so feedback belonged there too.
Solution: The daily Operator email summary now includes the number of open feedback items, whenever they were submitted.
Not only do we want our user's lives to be improved by using the app, we want to make sure our operators are well taken care of too.
Streamline Getting Verified
Problem: Users who started verification got stuck: the upload window opened once and never reopened. Users who needed to fix their name to match their ID had no way back to the identity fields.
Solution: The Get Verified flow is now one preparation page. One of the core feedback items when initially planning lookingforgroup.social was that people wanted to be able to trust that people are who they say they are. Since that is a safety issue, we want to make sure getting verified is straightforward and works well.
There is one form now that provides the instructions and expectations along with the form fields.
Reducing data transfer
Problem: Every page load (a new tab, a refresh, a tab the browser discarded overnight) fetched every dashboard list from scratch. The dashboard is where every visit lands, so those full fetches repeated for every user.
Solution: Each dashboard collection (My Clubs, accounts summary, notifications, contact methods) now saves its list and bookmark to localStorage, keyed by the active account. On load the saved list shows immediately, then an incremental fetch asks only for what changed since the bookmark. An account with nothing saved does a full fetch.
An incremental fetch only adds and updates, so we needed to consider removals from local storage as that has a limit of 5MB.
- User actions (leaving or disbanding a club, adding or removing a contact method) update the list right away.
- Changes made by others, like a manager removing a user from a club, arrive with a complete refresh that runs when the last full fetch is older than the cache TTL. The age counts from the last full fetch, so frequent visits cannot postpone it, and the check runs only when the collection is fetched, so a background tab makes no extra calls.
Keeping browser storage in check
Problem: The record cache saved everything it fetched to localStorage and removed almost nothing. For a user who rarely signs out, storage only grew toward the browser's per-site limit.
Solution: When the app starts in the browser, before any component reads the cache, a cleanup pass removes each saved record whose expires_at.
A read freshens the expires_at so it is not evicted from local storage.
This helps a user get their data quickly while also quietly purging old notifications, events, and clubs that you looked at but didn't join out of local storage.
What next?
lookingforgroup.social was created to get people connected in the real world. Now your dashboard and your inbox will remind you where to be. Club managers, go publish some events!
Head over to lookingforgroup.social and check it out.