Challenge
The Amazigh (Berber) community, concentrated in Algeria and spread across its diaspora, had no matchmaking platform built around its own cultural and religious values. Mainstream dating apps are built for casual swiping, not for people looking for a serious, marriage-focused relationship inside a specific cultural context. Language, regional origin within the Amazigh community, and profession needed to be part of how two people are matched from the start, not generic bio text added as an afterthought.
Approach
We treated this as a matchmaking product first and a dating app second. The data model was planned around what actually matters for intentional matching: origin, spoken language, and profession, captured during onboarding rather than left for a user to type into a free-text bio later, so filtering and matching logic has something structured to work with from a person’s very first session. The app was built in FlutterFlow with a Firebase backend (real-time database and authentication), which let the app ship on Android quickly while keeping the data layer standard enough for a developer unrelated to the original build to pick up later if needed.
What we built
- An onboarding flow that captures region of origin, spoken language, and profession as first-class profile fields, not generic bio text
- A discovery screen with pass, like, and favourite actions rather than a plain swipe-left/right, so a user can signal interest at more than one level
- A friend-requests and connection flow alongside the match flow, for a more deliberate way to connect than a disposable swipe match
- In-app messaging between matched and connected users
- Firebase Authentication and a real-time database, with the schema structured around the app’s actual matching criteria rather than a generic user table
- Submission to Google Play under the client’s own developer account
Outcome
THAFATH is live on Google Play, serving a community mainstream matchmaking apps do not build for. The client owns the Google Play listing, the Firebase project, and the FlutterFlow project outright. This is presented as project work; no install or usage figures are published without the client’s written approval.