Firebase and Next.js Deployment Basics for Small Teams

Use separate Firebase projects for development and production when the application handles real customer data. This makes it possible to test rules, Storage uploads, and authentication changes without placing production records at risk.

Store public Firebase configuration in environment variables, but remember that client configuration is not a secret. The real boundary is enforced by Authentication, Firestore rules, Storage rules, and carefully scoped admin credentials.

Keep firestore.rules and storage.rules in version control, review them like application code, and deploy them through an explicit Firebase CLI command. A successful application build does not prove that the backend rules are correct.

Test the main user journeys after deployment: create a quote, upload a supported file, submit a payment proof, and confirm that unauthenticated reads are rejected. Small end-to-end checks catch configuration drift quickly.

Add clear loading and failure states around Firestore and Storage calls. When a service is unavailable, a useful message and a retry path are far better than a silent form that appears to do nothing.