Optimize Live Streaming for "Meet9ja" App

Meet9ja – Live Streaming & App Performance Optimization We are looking for an experienced Flutter + LiveKit + PostgreSQL developer to optimize our existing social/live-streaming app. Main Issues Users Are Experiencing 1. Excessive Data Consumption During Live Streaming Users are actively complaining that the app consumes too much mobile data when they are watching a live stream or going live themselves. * Going live consumes a significant amount of mobile data. * Watching live streams also consumes excessive data. * We need to optimize video/audio transmission, bitrate, resolution, adaptive streaming, and network usage. * Data consumption should be reduced significantly while maintaining acceptable live-stream quality. 2. Phone Overheating & Battery Drain Users are also reporting that their phones heat up and battery drains quickly when: * Hosting/going live. * Watching live streams. * Using the live feature for extended periods. We need to identify what is causing excessive CPU, GPU, memory, network, and video-processing usage and optimize it. 3. Excessive LiveKit Costs Our LiveKit costs are currently too high. The developer needs to audit the implementation and identify unnecessary usage, including: * Unnecessary connections. * Connections that remain active after users leave. * Excessive bandwidth usage. * Recording/auto-recording usage where unnecessary. * Inefficient media configuration. * Unnecessary background processes or network activity. The goal is to significantly reduce LiveKit costs without compromising the live-streaming experience. 4. Excessive Data/Network Usage Outside Live Streaming The app also appears to consume mobile data during normal app usage, even when users are not watching or hosting a live stream. Please investigate: * Unnecessary API requests. * Repeated database/API calls. * Excessive polling. * Media automatically loading when it isn’t needed. * Poor caching. * Background network activity. * Unnecessary listeners/connections. 5. Overall App Performance We also want a complete performance audit to identify: * Memory leaks. * Excessive CPU usage. * Slow loading. * Unnecessary database/API requests. * Inefficient Flutter code. * Poor caching/pagination. * Background processes. * Excessive battery consumption. Live Streaming Requirements The developer should specifically optimize LiveKit and the live-streaming architecture so that: * Hosts use less data while going live. * Viewers use less data while watching. * Battery consumption is reduced. * Phone overheating is reduced. * LiveKit bandwidth/usage is reduced. * Users are properly disconnected when they leave a live. * No unnecessary LiveKit connections remain active in the background. * Video quality remains stable and acceptable. * Existing live features such as audio, video, comments, gifts, and interactions continue working. Important This is an existing production app with real users. Users are already complaining about excessive data consumption, battery drain, and phone overheating during live streaming. I am not looking to rebuild the app from scratch. I need a developer who can audit the existing implementation, identify the actual causes, and optimize the system properly. Tech Stack * Flutter * LiveKit * PostgreSQL * Existing backend/API infrastructure * iOS & Android Developer Requirements Please apply only if you have strong experience with: * Flutter performance optimization * LiveKit/live-streaming optimization * Video/audio streaming * Mobile network optimization * Battery/CPU/memory optimization * API/backend optimization * PostgreSQL * iOS & Android performance The developer should provide a before-and-after comparison where possible, showing improvements in data consumption, battery/CPU usage, LiveKit usage/cost, and overall app performance. What I Expect From the Developer * Proper technical audit before making major changes. * Clear explanation of what is causing the excessive costs and resource usage. * Measurable improvements in LiveKit cost, mobile data consumption, battery usage, overheating, network requests, and overall performance. * No breaking of existing features. * Proper testing on both Android and iOS. * Clean, maintainable code.