Marketplace
LConnect
One app for both sides of Egypt's creative industry: talent get scouted, casting offices post briefs and book studios.
- Client
- App Blender
- Year
- 2025
- Scope
- App, marketing site, back-office
- Platforms
- iOS · Android · web
The problem
Two sides of Egypt's creative industry that mostly found each other through WhatsApp groups and word of mouth.
Talent — actors, models, crew — needed somewhere to put their work where the people who hire actually look. Casting offices, production houses and agencies needed to post briefs, find people, and book the studios a shoot needs. Both halves existed; the connection between them was informal and lossy.
What I built
The screen
- iOS and Android app (Ionic, Angular)
- Marketing site
- Moderation back-office
The logic
- C# / .NET API
- SignalR for booking and scouting
- JWT auth
The data
- Talent profiles and their work
- Casting briefs and studio bookings
- Moderation records
A cross-platform app shipped to iOS and Android from one codebase — Ionic and Angular on Capacitor. Talents build a profile and post work; casting offices and production houses post briefs, scout, and book studios or locations in-app.
Behind it, a C#/.NET API with SignalR for realtime and JWT for auth. Booking and scouting are conversations under time pressure, so a status change landing a page-refresh later isn't good enough.
I also built the marketing site and the moderation back-office. That last one matters more than it sounds: a marketplace where anyone can post needs someone able to take things down, and that surface has to exist from the start.
One hard decision
One codebase for both app stores
One team, two app stores and a product still finding its shape. Capacitor let the same TypeScript ship to iOS and Android, so feature parity came free instead of being something to maintain. The cost is a less native feel, and the part that would have suffered most from it, realtime messaging, runs on SignalR rather than on anything platform-specific.
What I'd change now
I'd put an audit trail under the moderation back-office from the first release. Taking a post down is the easy part. Showing later who took it down, and why, is what a marketplace needs when someone disputes it.
Stack
- Ionic
- Angular
- Capacitor
- TypeScript
- C# / .NET
- SignalR
- JWT auth