A video-first dating product can look deceptively simple from the outside. A member creates a profile, discovers someone nearby, expresses interest and starts a conversation after a match. The visible flow is only half the product.
HEY Africa had to handle what happened around that flow: uploaded media, relationship states, reports, appeals, blocking, notifications and the administrative work behind them. SKWD carried those concerns through product and technology delivery, and the connected system reached production.
Video changes the operating model
Video gives people more context than a static profile. It also creates more material to process and review. Location-aware discovery adds another layer of sensitivity, and a dating product has to consider what can happen after an online interaction moves offline.
That means trust and safety cannot be added as a policy page after launch. It affects data handling, permissions, user states, moderation queues, incident workflows and the structure of the administration product.
For HEY Africa, the member experience and the operating system were developed together. Profiles, discovery, mutual matching and chat were connected to media processing, reports and administration rather than delivered as separate product lines.
The back office is part of the customer experience
Members may never see the moderation tools, but they experience their consequences. A report that loses context, an unclear appeal or a media workflow that cannot be reviewed is still a product failure.
The same is true for engineering decisions. Upload handling, asynchronous processing, notifications and relationship states need to support the safety model. If those systems are designed independently, the operating team spends its time reconciling gaps between them.
The production delivery therefore had two audiences. Members needed a clear, responsive route from profile to conversation. Operators needed enough control and context to run that route responsibly.
What the completed work demonstrates
HEY Africa is a completed Scale case study. It demonstrates that SKWD could take a video-first proposition through product definition, mobile and backend delivery, media workflows, moderation and production release under one technical direction.
The classification describes the completed engagement. It does not claim that the service is currently operated, or publish user, revenue or present market-performance data. That boundary keeps the case study useful and accurate: it records what was delivered without turning delivery history into a different kind of claim.
For a new social-discovery or media-intensive product, the reusable lesson is straightforward. Design the user flow and the operating response together. Trust and safety are not support functions around the product. They are part of the product architecture.