A push notification model usually breaks in one of two ways: a second phone stops receiving anything, or notifications keep arriving for the account that just signed out. Both come from storing one push address per user. Store one row per app installation instead, with the user ID as a field, and someone with a phone and a tablet has two rows that a single query returns.

The sign-out half has an ordering trap. Delete the installation row while the user is still signed in, then call signOut. A security rule that compares the row owner to the signed-in user refuses the delete once there is no user left to compare against, and the device keeps pointing at the previous account.

The full write-up covers the Firestore rules, the Flutter registration listener, a server cleanup that handles both unregistered error codes, and an acceptance sequence to run on two test installations.

Great breakdown! The sign-out timing is such an easy detail to overlook, but it can cause real issues. 👏

🚀 Meet FLOWPILOT, A Client Operations Platform Built with Base44

I built FLOWPILOT to help freelancers and small agencies simplify client management, project tracking, and everyday workflows.

The platform brings client requests, projects, tasks, and workflow management into one organized dashboard.

With Client Intake, Workflow Board, Automation Center, and Client Portal features, FLOWPILOT is designed to reduce repetitive work, improve project visibility, and make client collaboration easier.

Using Base44, I turned this concept into a functional web application, focusing on a clean interface, practical features, and an intuitive user experience.

Excited to share my entry for the #Base44Challenge!

I'd love to hear your thoughts and feedback. #Base44Challenge #Base44 #WebApp #SaaS #ProductDesign #UIUX