À propos
Project Overview
We built a Flutter (Web + Mobile-ready) application using Firebase as backend (Auth + Firestore).
The app is a building/property management system with two roles:
Admin (Building Manager)
Resident
The system includes:
Account creation and login
Role-based routing
Create Building flow (admin)
Join Building via 24-hour invite token (resident)
Membership approval flow
Units management
Financial claims
Payments tracking
Notifications
Invite token lifecycle management
Dashboard views per role
The core architecture is in place.
However, after iterative changes and feature additions, some flows became fragile, and we need a senior expert to:
Audit the architecture
Fix broken flows
Improve stability
Validate security rules
Refactor authentication logic
Implement proper email OTP verification
Ensure long-term scalability
This is not a feature-building job.
This is an architecture stabilization + production hardening job.
What We Need
We need a Senior Flutter + Firebase Architect to:
Validate Overall Architecture
Review routing logic (GoRouter)
Review AuthController logic
Validate role locking (admin vs resident)
Ensure deterministic navigation (no loops / no ghost redirects)
Remove legacy logic and unused paths
Standardize intent-based authentication
Fix Account Creation + Email OTP Verification
Current problem:
We introduced email verification
It blocks users
No OTP system exists
No backend verification implementation
Flow is inconsistent
We need:
Proper email OTP implementation (6-digit code)
Secure OTP storage with expiry (Firestore or Cloud Functions)
Resend logic
Verification screen
Clean routing after verification
Backward compatibility for existing users
No dead states
No forced Firebase emailVerified dependency
Database Structure Validation (Firestore)
We need a professional review of:
Collection structure
Security rules
Token storage model
Role storage (adminOfBuildingId / residentOfBuildingId)
Invite token lifecycle
Query efficiency
Index requirements
CollectionGroup usage
Scalability risks
Multi-building scalability
Future analytics readiness
Current collections include:
users
buildings
buildingInvites
memberships
units (subcollection)
payments (nested)
claims
notifications
We want confirmation that:
This structure scales to thousands of buildings
Token system is clean
Security rules are consistent
No circular permission logic
No performance bottlenecks
Resolve Firestore Security Rule Instability
We have had repeated permission-denied issues due to:
Admin checks
Membership approval updates
Invite token reads
Notification queries
collectionGroup('payments')
We need:
A clean consolidated Firestore rule set
Minimal but secure
Clearly documented
Role-consistent
Production-ready
Fix Broken / Inconsistent Flows
Issues include:
Post-login routing conflicts
Intent routing overrides
Splash screen session conflicts
Token validation inconsistency
Admin invite page generating UI-only tokens
Membership approval permission issues
Email verification blocking
Backfill adminOfBuildingId failing
Resident/admin flow collisions
We want deterministic state transitions.
Dependency & Package Review
We need review of:
pubspec dependencies
Firebase packages
Flutter web compatibility
Hot reload stability
Router lifecycle
State management structure
Any anti-patterns
UX / UI Review
We want a professional audit of:
Create account flow
Join building flow
Admin invite management
Setup hub
Profile setup
Notification structure
Error messaging consistency
Empty state UX
Loading state UX
Form validation UX
Not redesign — but enhancement suggestions.
Codebase Cleanup
Remove dead logic
Remove legacy invitationCode system
Remove deprecated routing
Remove duplicated validation
Simplify auth flow
Standardize logging
Add structured error handling
Current Tech Stack
Flutter (Web-first)
GoRouter
Firebase Auth
Cloud Firestore
Firestore Security Rules
No Cloud Functions yet (optional)
Stateless + Controller-based architecture
Custom AuthController
Intent-based routing (recently added)
Expected Deliverables
Full architecture review document
Cleaned authentication flow
Working OTP email verification system
Consolidated Firestore rules
Database scalability validation
Fixed broken navigation loops
Stable create/join flows
Documented system state diagram
Refactored invite token lifecycle
Clean final production-ready branch
Ideal Candidate
We are looking for someone who:
Has built production Flutter + Firebase apps
Understands state machines and routing architecture
Understands Firestore scalability
Has experience with multi-tenant systems
Has experience designing secure OTP flows
Can audit existing code (not just build new features)
Writes clean, minimal, scalable logic
Can explain architecture decisions clearly
Senior-level only.
Project Scope
Estimated:
2–4 weeks engagement
Architecture + stabilization phase
Potential long-term collaboration
When Applying, Please Include
Links to production Flutter apps you've built
Experience with Firestore scalability
Experience implementing OTP systems
Experience fixing broken routing flows
How you approach auditing an unstable app
Optional Add-On
If you also have experience with:
Firebase Cloud Functions
Email services (SendGrid / Mailgun)
CI/CD for Flutter web
Monitoring and logging
Please mention it.
Contract duration of 1 to 3 months.
Mandatory skills: Android, iOS, User Authentication
Compétences linguistiques
- English
Avis aux utilisateurs
Cette offre provient d’une plateforme partenaire de TieTalent. Cliquez sur « Postuler maintenant » pour soumettre votre candidature directement sur leur site.