
Exclusive 200-member influencer communities — live auctions, Dyte WebRTC, Branch deep-links, 80+ API endpoints.
Built a real-time creator-economy platform where influencers host exclusive 200-member communities with direct fan mentorship. The Flutter app uses GetX against a Node.js/Express API and MongoDB/Mongoose. Live bidding, group chat, and anonymous audio run through Socket.IO with dedicated event rooms; video for auctions and gossip uses the Dyte WebRTC SDK with REST-driven room lifecycle.
Flutter (GetX) → Express/MongoDB (80+ endpoints) → Socket.IO (bid rooms, chat, gossip) → Dyte SDK (WebRTC) → Branch.io → AWS S3 (media + Sharp thumbnails) → Firebase (FCM, Auth, Crashlytics, Analytics) → Bull/Redis → Mailjet + Nodemailer → Clarity + Smartlook.
Concurrent live-bid synchronization across hundreds of participants; 80+ Express endpoints requiring careful organization; anonymous audio session state across multiple Dyte rooms; coordinating FCM with auction lifecycle; and Branch.io deep-links from social into the right Flutter screens.

Community creation with member caps, invites, and role-aware access for hosts and fans.
Socket.IO bid rooms with real-time price updates and isolated state per auction.
Managed WebRTC for auction sessions and anonymous gossip with Dyte REST for rooms and recording.
Deep-links from Instagram, Twitter, and other channels into posts, profiles, live bids, and communities.
S3 uploads with Sharp thumbnails; FCM per-device tokens; Bull/Redis for email campaigns and scheduled events.
Express endpoints across communities, auctions, payments, profiles, analytics (Clarity, Smartlook), and admin — enough surface area to ship creator economy features without fragmenting into microservices prematurely.
Express endpoints across communities, auctions, payments, profiles, analytics (Clarity, Smartlook), and admin — enough surface area to ship creator economy features without fragmenting into microservices prematurely.




Managed video with recording and participant APIs versus hand-rolling TURN/STUN and server orchestration.
Socket.IO event rooms isolated bidding state so price fan-out stayed predictable at scale.
Cross-platform routing into specific Flutter screens for social acquisition campaigns.
GetX accelerated Flutter delivery versus heavier state stacks for a deadline-driven product.
Guaranteed delivery and retries for email and lifecycle jobs instead of fire-and-forget HTTP.
PM2 plus disciplined route splitting kept the large Express codebase operable in production.
We take on a small number of projects at a time. If the problem is hard, we're interested.