Mobile app development for businesses in Kurdistan and Iraq

Apps built in Sulaymaniyah, for the people who will actually use them

Enzziro is a software company in Sulaymaniyah (Slemani) that designs and builds mobile apps for businesses in the Kurdistan Region, across Iraq and beyond. We take an app from the first conversation to a listing in the App Store and Google Play, and we stay on for the updates that follow.

Most of the apps we build have to work in more than one language. A customer in Erbil may want Kurdish, a supplier in Baghdad Arabic, and a partner abroad English, all in the same app. We plan for that from the first screen, not as a translation pass at the end.

What we build

• Customer apps that put your prices, products, bookings or accounts in your customers' pockets.
• Internal and field apps for staff who work away from a desk: collectors, drivers, sales teams, inspectors.
• Companion apps for an existing web platform or back office, sharing the same accounts and data.
• MVPs: a focused first version that tests the idea with real users before you commit to the full product. See what an MVP is.

Built for Kurdistan and Iraq

Building for this market brings requirements that a template app or an overseas agency often gets wrong:

• Arabic and Kurdish, right to left. Sorani Kurdish and Arabic both run right to left. Layouts, icons, number formats and text input have to mirror properly, not just have their words swapped.
• Three languages in one app. English, Kurdish and Arabic side by side, with the reader choosing, and content your team can update in each.
• Dollars and dinars. Prices shown in the currency your customers actually think in. Some apps need both.
• Connections that drop. Screens that load quickly on a mobile network, and flows that recover when the connection doesn't.

Examples from our work

• Bawan Precious Metals: a free iOS app for Bawan Gold in Sulaymaniyah. It publishes live gold, coin and bullion rates, recalls the price on any past date, and runs in English, Kurdish or Arabic. It is live on the App Store for iPhone, iPad, Mac and Apple Vision.
• ScreenTrak: our own TV and anime tracker for iOS and Android, built with React Native and Expo, TypeScript and PostgreSQL. Users can export or delete their data themselves.
• Wa7a: a rental marketplace for a client in Dubai, with a mobile app and a website covering listings, identity checks, lease workflows and in-app messaging.

Native or cross-platform?

There are two main ways to build a mobile app, and the right one depends on what the app has to do:

• Native apps are written separately for each platform, in Swift for iOS and Kotlin for Android. That suits apps that lean hard on the device (camera, sensors, Apple-only features) or that must feel exactly at home on one platform.
• Cross-platform apps share one codebase across iOS and Android, using Flutter or React Native. For most business apps, this means one team, one release schedule, and a lower cost of change.

We'll recommend one or the other after we understand the app, and tell you why. The glossary explains the difference between a native app and a hybrid app in more detail.

How a project runs

1. Discovery. We start with a call with the engineers who will build the app, not a salesperson. We agree what the first version must do, and you get a written scope, a technical plan and a timeline.
2. Clickable prototype. You tap through the screens and approve the flow before we write the complex code.
3. Build in sprints. You get weekly updates and a test build on your own phone as the app takes shape.
4. Launch. We prepare the store listings, handle App Store and Google Play review, and train your team on anything they will manage.
5. After launch. Operating-system updates, fixes and new features, on whatever arrangement suits you.

The process page covers this in more detail.

Technology we use

• iOS: Swift. Android: Kotlin.
• Cross-platform: Flutter, React Native with Expo.
• Back ends and APIs: Python, Node.js with TypeScript, and PostgreSQL, on cloud hosting such as AWS.
• Push notifications, analytics, crash reporting and automated release pipelines. See beta releases for how test builds reach you before launch.

What affects the cost of an app

We don't publish a price list, because two apps with the same name can differ tenfold in effort. The things that move the cost most:

• How many roles the app serves. A customer app is one thing; a customer app plus a staff app plus an admin panel is three.
• Platforms. iOS only, Android only, or both, and whether a web version is needed too.
• Integrations. Payments, maps, your existing systems, third-party data such as live prices.
• Languages. Each additional language adds design and content work, especially when it runs right to left.
• What already exists. A new product costs more to start than an app added to a working back end.

Describe your project on the start a project page and we will come back with a scoped estimate.

Frequently asked questions

Do you build for both iPhone and Android?

Yes. We build for iOS, Android or both. Where it makes sense, one cross-platform codebase covers both, and a single app can also run on iPad and Mac.

Can the app be in Kurdish and Arabic as well as English?

Yes. This is the norm for our apps, not an extra. Bawan Precious Metals, for example, runs in English, Kurdish and Arabic, with the layout mirrored for right-to-left reading.

Will you publish the app to the App Store and Google Play?

Yes. We prepare the store listings and screenshots, submit the builds and deal with review feedback. The app is published under your developer account, so you own the listing.

Can the app take payments in Iraq?

Usually, yes. Which payment method fits depends on your customers: cards, a local wallet or cash on delivery. We integrate the provider you hold a merchant account with, as long as it offers an API. We confirm this during discovery, before it goes into the scope.

Who owns the code?

You do. The source code, the store listings and the accounts behind them belong to your business.

Do you maintain the app after launch?

Yes. Apps need regular updates to keep working on new iOS and Android versions. We agree an ongoing arrangement at launch, whether that is on-call fixes or a planned roadmap of new features.