Petdagogy: Building a Pet Care SaaS with Flutter & Firebase

Firestore reads, almost always. Community feeds are the worst offender: a naive query re-reads the whole thread every time someone opens it. Petdagogy fixed that by denormalizing feed data into precomputed documents and paginating hard. Your Firebase bill tracks document reads, not user count. Design the reads first.

Because booking is transactional and habit isn't. Someone opens a booking app when they need a sitter. They open a community because something happened to their dog. Community changes the reason to launch. The cost is real: moderation, reporting flows, and someone actually reading the reports.

Through the stores, on mobile. Selling digital access means their billing and their cut, and no workaround survives review. Keep entitlement state on your backend, never on the device. That way one subscription follows the user across phones, tablets and the web, and support can fix a bad purchase without a reinstall.