Android Social Networking App Build

@C0RETECHIES

Hi, You need an Android-only social engine focused on real-time user connectivity. Operationally, this requires a low-latency feed mechanism, resilient media upload pipelines, and instant event propagation for messaging and engagement, all wrapped in Material Design. Technical approach: We will build natively in Kotlin using MVVM and Jetpack components. Firebase is optimal here: Firebase Auth for seamless login, Firestore for real-time document sync, Cloud Storage for media, and FCM for push notifications. We'll add Crashlytics for day-one analytics. Core modules: - Identity: Multi-provider login and profile state management. - Media Pipeline: Asynchronous background uploads with compression to prevent UI blocking and crashes. - Feed Engine: Paginated feed queries with local caching to guarantee <2s load times. - Notification Pipeline: Event-triggered Cloud Functions routing instant payloads to targeted devices. Relevant systems: - Fanhut: Real-time social feeds, caching, and instant interactions. - Encrypted Chat Suite: Native Android messaging and push delivery architecture. Implementation strategy: We begin with auth and feed architecture to validate the load speed requirement. Next, we implement the media pipeline and real-time chat/FCM. Finally, we perform strict memory profiling to ensure a clean, warning-free AAB build for Play Store release. Regards, Rohit

@codeandcommand

Building the core social feed and video upload flow is where most Android builds stall once real users start posting. I would use Kotlin with a Room and Retrofit setup for offline caching, and handle video uploads through a background WorkManager queue so nothing fails on weak connections. Can start today, working feed and upload flow ready in 6 days. Budget and timeline here are starting points based on the post as written. Once we talk through the full feature list, both may shift. Want me to send a quick scope doc so we can get moving?

@naeem1114

Video uploads often hit a memory limit on older Android phones, which can crash the feed. I’ll compress the video on the device using a Kotlin coroutine and stream it directly to Firebase Storage to keep the heap low. At the same time I’ll add a retry wrapper around the Cloud Function call so intermittent network drops don’t break the post. A common pitfall is leaving LiveData observers attached after a fragment is destroyed, which leads to stale UI updates. I’ll bind the feed view model with Jetpack’s viewLifecycleOwner and clear the listeners in onDestroyView to keep the app clean. Ready to start right away and get the core features running on the Play Store.