It depends on scope. A focused MVP can take weeks (often in a 4–8 week range). A multi-platform product can take months. The estimator is a first range; the calendar is set after discovery.

Arabic yes — real RTL when that is the product language. Payments follow the market: local rails such as CMI in Morocco; Apple Pay and Google Pay when the product and acquirer allow it; Mada when the audience is in Saudi Arabia. We do not add a gateway because it looks good on a slide.

Yes. When the project is complete and agreed amounts are settled, you receive the source code, files and assets for your product. Ownership is written into the agreement.

After scope, we write a proposal tied to milestones: start of work, a clear stage such as design approval, then launch. Percentages are set in the agreement for that project — not a public rate card.

Launch is the start of the relationship. Stores or web within scope, then X CARE for fixes, store updates, features and performance. Consulting or CTO as a Service if technical decisions need to continue.

Yes. We help cut the idea down to a testable MVP rather than building everything at once. Consultation, the estimator and the offers page are built for that start.

There is no honest price before idea, platforms, features and existing assets are understood. The offers page shows a preliminary MAD and USD range — not a quote. A written estimate comes after scope.

Yes. Often with Flutter when one product is the right call.

Yes, when it serves the product, budget and both stores.

Yes — one of our strongest offers. We start from reality.

Yes, when it creates value. Not as decoration.

Yes. APIs, Firebase or otherwise, and admin when needed.

Yes, through X CARE on an agreed monthly cadence.

Yes. An MVP tests a hypothesis.

Yes, preparation and submission within scope. Official accounts stay yours.

Yes. Consulting and CTO as a Service.

Yes, from booking or contact. A preliminary look is not a full technical audit.