Planny
Production platform for driving schools: student management, lesson booking, instructor scheduling, progress tracking, notifications, and multi-role access.
Flutter, iOS, Android
Flutter Firebase Development Across Auth, Data & Notifications
Firebase issues can look like mobile UI bugs. I review the client configuration, user identity, access rules, and environment together so the fix addresses the failing workflow.
Discuss your Flutter Firebase issueAccount state and data access are one workflow
Trace sign-in, token refresh, sign-out, and the data each role can read or change. Firestore and Storage rules need explicit access expectations. Review offline behavior and avoid treating a cached result as proof that the server accepted a write.
Debug notifications by delivery stage
Separate permission, registration, token storage, delivery, and app handling. Android success does not confirm the iOS configuration. Check the affected build and Firebase project before changing message-handling code.
Keep environments and diagnostics distinct
Use clearly identified development and production configuration. Review Functions where they are part of the backend, and agree which analytics and crash events are useful without including private data. Configuration migrations need a rollback plan and a real-device check.
Related product work
Fiedk | في ايدك
Multi-vendor marketplace for restaurants, grocery, and commerce: customer and vendor roles, catalogs, ordering, payments, tracking, location, and notifications.
Flutter, iOS, Android
Before we start
Can you fix Firebase issues without rebuilding the whole app?
Often the necessary change is confined to configuration, rules, or one integration. First reproduce the issue and locate the failing boundary. Some client changes still require a new app release.
Are the linked projects proof of a specific Firebase feature?
They demonstrate the relevant mobile workflows. Their case studies do not attribute every backend feature to Firebase.