The problem
Finding dependable local workers and agreeing on terms can be fragmented and informal. The opportunity was not to replace those relationships, but to make discovery, expectations, trust signals, and communication clearer for both sides.
The response
I designed and built a cross-platform marketplace MVP covering worker and job discovery, applications and invitations, mutual agreements, portfolios and reviews, private communication, identity signals, safety controls, and offline resilience.
Decisions that shaped the product
- 01
Trust signals, not trust guarantees
Identity verification is deliberately bounded. Reviews connect to real work relationships, and the product never treats a badge as proof of skill or safety.
- 02
Mutual terms before private access
Clients and workers accept an immutable agreement before exact addresses become available. Privacy follows the relationship state.
- 03
Design for local constraints
French and Arabic, XAF pricing, multiple workers per job, clear offline states, and retry-safe actions are part of the core model rather than localization added later.
Implemented evidence
- Role-free client and worker participation with discovery, proposals, invitations, and agreements.
- Public and private data boundaries enforced through Firebase rules and trusted gateway contracts.
- Portfolio, review, safety, moderation, identity, account-deletion, notification, and offline-resilience flows.
- Automated unit, interface, emulator, and security-rule test infrastructure plus a release gate.
Current limits
- The product is still in development and has no claimed production adoption or market impact.
- Several production capabilities require trusted server adapters and final provider configuration.
- Device-level release validation must be completed before the MVP can be called release-ready.
Responsible product leadership means defining what a system must never imply. In Khidme, the limits around identity, safety, privacy, and outcomes are as important as the visible features.