Goose Mobile — Social Media + Telecom Platform
A full-stack mobile platform combining a TikTok-style short-form video social network (Shortzz) with a built-in mobile carrier service — letting users post reels, go live, and manage eSIM/SIM plans, billing, and an embedded banking account all in one app.
Overview
Goose Mobile is a full-stack mobile platform that fuses three domains into one app: a TikTok-style short-form video social network (Shortzz), a mobile carrier service (eSIM/SIM plans, billing, activation), and an embedded banking account (Unit-powered deposit accounts, debit cards, KYC, ACH). Built with Flutter on a Laravel API, with real-time live streaming (Zego), AR filters (DeepAR), and payments via Adyen — plus a full admin CMS for SIM inventory, order fulfilment, and moderation.
Key Features
- Short-form video feed (reels), stories, and live streaming with co-hosting, AR filters (DeepAR), and an in-app video editor.
- eSIM/SIM plan browsing, ordering, activation, and lifecycle management via carrier API integration.
- Embedded banking: Unit-powered deposit accounts, debit-card issuance, KYC verification, ACH transfers, and transaction history.
- Payment processing via Adyen (cards, Apple Pay, Google Pay) with webhook-based order confirmation.
- Creator monetization: coin wallet, virtual-gift sending, and coin-withdrawal requests via multiple payout gateways.
- Full admin CMS: SIM inventory management, order fulfilment, plan CRUD, user moderation, site settings, and an analytics dashboard.
Challenges & Solutions
Architecting a single platform across three distinct domains — social media, telecom, and banking — required clean service-layer separation (IspwnService, UnitService, AdyenService) so each integration could be developed and swapped independently without touching controllers.
Real-time features (live streaming via Zego, chat via Firebase Firestore, push via FCM) run on separate infrastructure from the Laravel API, to avoid coupling latency-sensitive streams to the REST backend.
SIM activation relies on async webhooks from the carrier API, so order state is managed as a state machine updated by webhook callbacks rather than synchronous responses.
Results & Impact
?? Add real outcomes (users, activations, revenue) when available.