FlutterFlow Developer — Hospitality Operations App (Prototype to Production)

I’m the systems architect behind a brand operating system for a luxury short-term rental company — SOPs, field tools, vendor accountability frameworks, training programs, the full infrastructure. What I’m not is an app developer. I need a technical partner who can take a well-documented architecture and build it in FlutterFlow. The app: A native iOS + Android team-facing operations app for a hospitality brand operating across multiple U.S. markets. The app is how Market Managers, turnover vendors, maintenance crews, partner-owners, and leadership interact with the operating system daily. Tech stack: • FlutterFlow (frontend) • Firebase — Auth, Firestore, Cloud Storage, Cloud Functions, Cloud Messaging • Airtable API integration (operational data) • Hostaway PMS API integration (property and reservation data) • 7 user roles with distinct experiences • Interactive checklists with photo capture and offline support • Push notifications with severity-based routing The engagement: • Project 1 (fixed-fee): Combined foundation + reference library prototype — login, role-based routing, searchable SOP library with Firestore backend. This is how we test the working relationship. • Project 2+: Iterative milestone-based builds toward production — checklists, API integrations, dashboards, notifications, app store submission • Future state: Ongoing retainer for maintenance and feature development What I bring: • Full architecture documented — every screen, every data flow, every API call, Firestore schema for 10+ collections, Cloud Functions written • Deep operational context — I know exactly what every feature needs to do and why • Firebase project created, test users configured, Build 1 (login + routing) started What I need from you: • Strong FlutterFlow experience with production apps • Firebase proficiency — Firestore, Cloud Functions, Auth, Cloud Messaging • REST API integration experience • Understanding of offline-first mobile architecture • Clean project structure someone else can read • Proactive communication — ask before assuming, surface blockers early What this isn’t: • A tutorial project or clone • A one-off gig with no follow-up • A situation where I’ll be micromanaging your technical decisions — I trust your expertise on the build side, you trust mine on the systems side To apply: • Share 2-3 FlutterFlow projects you’ve built (production preferred) • Briefly describe your Firebase and API integration experience • Tell me what you’d want to know before quoting Budget and timeline details shared after initial conversation.