Emilo
A social platform's commerce and dating modules.
Emilo Ventures Pvt Ltd · 02/2026 – Present





Overview
Emilo is a social media platform combining community, commerce and connection. As the current focus of my Senior Flutter Developer role, I'm responsible for architecting and building major feature modules end to end, including a full gifting/commerce flow and a real-time dating experience, alongside native platform integrations and the CI/CD pipeline they ship through.
My Role
- Architected and built the complete Gift Section module from scratch — product catalog, gift details, search & filters, wishlist, cart, order placement, cancellation and return flows — using BLoC and Clean Architecture.
- Developed the Soft Corner dating module: custom matchmaking UI, animated interactions, crush matching, and real-time notification-driven navigation on Socket.IO.
- Built native camera integration (MethodChannel + CameraX), app usage analytics, event management, business pages and product reporting.
- Delivered the Explore and Profile modules with full localization (l10n) support.
- Set up Git/GitHub-based CI/CD with flavor-based builds for UAT, beta and production.
Key Features
Engineering Challenges
Real-time notification-driven navigation
Soft Corner's crush-matching flow needed the UI to react instantly to server-pushed events — deep-linking a user straight into the right screen and state from a Socket.IO notification without breaking BLoC's unidirectional data flow.
Native camera bridging
Camera capture required going beyond Flutter's plugin ecosystem into a custom MethodChannel bridge to CameraX on Android, coordinating lifecycle and permission state between the Flutter and native layers.
A full commerce lifecycle from zero
The Gift Section's order placement, cancellation and return flows had to be modeled and built from scratch inside Clean Architecture boundaries, keeping each state transition testable and independent of the UI.
Flavor-based release pipeline
Shipping UAT, beta and production builds from one codebase meant structuring flavors, environment config and CI/CD so each channel stayed isolated and reproducible.
Technologies
Technical Architecture
How the pieces I own fit into the application's data flow.
- 01Flutter UIFeature-first widgets for Gift Section, Soft Corner, Explore & Profile
- 02State ManagementBLoC — unidirectional state, event-driven
- 03RepositoryClean Architecture repository layer abstracting data sources
- 04API / Socket.IO / NativeREST APIs, Socket.IO real-time channel, MethodChannel to CameraX
- 05Backend & ServicesEmilo backend services & device camera hardware