How to Choose an App Development Company in Kuwait: 8 Things to Check
Choose an app development company in Kuwait by checking what you can verify yourself: apps published on the App Store and Google Play under the company's legal name, a clear answer on who handles store submission and under whose account, Arabic that works properly, experience with Kuwaiti payments such as KNET, and a plan for the years after launch. Here is how to check each one before you sign.
By UPGRADE·Published
1. Ask for apps you can verify on the stores
Every listing on the App Store and Google Play shows the name of the developer account that published it, and both stores have a public developer page listing every app from that account. That makes app development one of the few services where you can check a portfolio in minutes: search the company's legal name on Apple's and Google's developer pages and see what is actually live.
Screenshots and design mock-ups prove that someone designed screens, not that the company shipped a working app. If the apps a company shows are published under its clients' names, which is normal and often correct, ask for one or two clients you can call. A good developer will be glad you asked.
Search the company's legal name on Apple's and Google Play's developer pages
Install at least one of their apps and use it as a customer would
Ask which parts they built: the app, the dashboard, the backend or all three
2. Find out who handles App Store and Google Play submission
Many quotes end at “app delivered”, which can mean a file and a handshake. Getting that file onto both stores is a project of its own: developer accounts, a D-U-N-S number for your company, store listings in Arabic and English, privacy declarations, content ratings, demo accounts for the reviewers and screenshots in the sizes each store accepts. Then come the reviews, and sometimes rejections.
Ask directly: who submits the app, who answers the reviewers, and who fixes and resubmits it if it is rejected? Also ask when they last had an app rejected and what they changed. Every team that publishes regularly has an answer. Ours: Apple once rejected iPhone screenshots that had been captured on an Android emulator, and we now capture every store image on the platform it is going to.
3. Make sure the app is published under your company's account
Whoever owns the developer account owns the listing: its reviews, its download history and the ability to update it. If a developer publishes your app under its own account, you depend on that developer for every future release. Both stores allow apps to be transferred between accounts, but a transfer involves paperwork, steps on both sides and new signing credentials. We have done one, and it is far easier to publish under the right account from the start.
The better arrangement is for your company to enrol with Apple and Google as an organisation and give the developer access through the stores' team roles. The listing then shows your company's name, and you can change developers without moving the app.
4. Test their Arabic, not just their translations
Arabic support is more than translated text. The whole layout must mirror from right to left: back arrows, progress bars, swipe directions and lists that scroll sideways. Mixed text, such as an Arabic sentence containing a product code or a price in KWD, has to stay readable. Arabic fonts need more line height than Latin ones. Getting this wrong makes an app feel foreign to the customers it was built for.
Ask to see one of their apps in Arabic on a real phone, and check that it reads as if it was designed in Arabic first. Ask how the app decides its direction: an app that switches direction after it has already drawn the screen can end up with taps landing in the wrong place, a bug we have had to fix in an app we took over.
5. Check experience with Kuwaiti payments
Customers in Kuwait expect KNET, so a store or booking app usually needs a local gateway such as MyFatoorah, which supports KNET, cards and Apple Pay. Apple allows payment through your own gateway when you sell physical goods or services used outside the app, such as groceries, deliveries and bookings, but requires its own in-app purchase for digital content and features unlocked inside the app. A developer should know which side of that line your app is on before writing any code.
Also ask how they handle the uncomfortable cases: a payment that succeeds while the order fails to save, refunds when an item is out of stock, and partial payment from a wallet balance. These are the cases that generate support calls.
6. Ask about the dashboard behind the app
Most business apps are only half the product. Someone has to add products, change prices, assign orders, answer customers, issue refunds and read reports, and that happens in a web dashboard. Quotes that describe only the app's screens often leave the dashboard vague, and it is where your team will spend its day.
Ask to see a dashboard they built and who uses it. In our own products, Salwa's dashboard runs orders, stock, payments, refunds and staff permissions, and Hodori's runs each school's classes, students, staff and reports.
7. Ask what happens after launch
Apps need regular work just to stay on the stores. Google Play raises the minimum Android version that apps must target every year, and in 2026 it began refusing updates whose native libraries didn't support 16 KB memory pages. Apple periodically requires new uploads to be built with recent tools. Signing certificates expire. An app that nobody maintains can become impossible to update without anyone noticing, until the day an urgent fix is needed.
Ask what maintenance includes, how fixes reach users (many can go out as over-the-air updates without a store review) and how they will tell you about store deadlines before they arrive.
8. Agree on source code, access and handover
Before you sign, agree in writing who owns the source code, where it is stored, and how you get access to it, the hosting, the database and the developer accounts. Ask for the credentials to be stored under your company rather than a personal email, and for enough documentation that another team could take over. You may never need it, but a developer who resists this is a warning sign in itself.
Warning signs
Any one of these is worth a direct question before you go ahead:
No apps you can find on the stores under the company's name or its clients'
The app will be published under the developer's account “for now”
Arabic is planned for a later phase
No clear answer on Google Play's target-API and 16 KB rules
A quote that doesn't mention the admin dashboard
No plan for rejections, resubmissions or yearly store requirements
Questions people also ask
Which app developers in Kuwait handle App Store and Google Play submission?
Ask every company you consider to show apps it has published and to confirm in writing that store submission, answers to reviewers and resubmissions are included. UPGRADE handles the full submission on both stores, and its own apps, Hodori and Salwa, are published under UPGRADE WEB DESIGN COMPANY on the App Store and Google Play.
How can I check whether a developer really built an app?
Look at the developer name on the store listing and on the store's public developer page. If the app is published under a client's name, ask the developer to put you in touch with that client.
Should my app be published under my company's account or the developer's?
Under your company's account. The listing, its reviews and its update history then belong to you, and you can change developers without transferring the app.
Do I need a D-U-N-S number to publish my company's app?
Yes, for an organisation account. Apple and Google both use the D-U-N-S number to verify that your company exists and that its legal name matches the account.
Is React Native good enough for a business app?
For most business apps, such as ordering, booking, delivery, attendance and field work, yes. It produces native iOS and Android apps from one codebase. Apps built around heavy 3D, augmented reality or unusual hardware may need a different approach.