An iOS app developer in Dubai, from the first build to App Store approval

Building the screens is the part people picture. The rest is Apple's: an app has to run well across the iPhones still in use, follow the Human Interface Guidelines closely enough to feel at home, declare exactly what data it collects, ask for permissions at the right moment, and pass App Review before anyone can download it. Each of those can delay a launch, and each is predictable if it is planned from the start.

I build iOS apps in React Native rather than Swift. The result is a real iOS app using Apple's own interface components, and the same code ships to Android, which matters to most businesses here. Where an app genuinely needs Swift, such as for heavy graphics or the newest Apple frameworks on day one, a native iOS developer is the better hire, and I will tell you before you commit.

Most apps are designed for the iPhone first, and that is right for customer apps. Sales teams are different. In property especially, the iPad is the presentation device: a sales manager sits beside a buyer and walks them through projects, floor plans and availability on a ten or eleven-inch screen. An iPhone layout stretched to that size wastes it.

So iPad layouts are designed for the larger screen, often with a list and its detail side by side, and tested in landscape, which is how tablets sit on a sales desk. For a tablet dedicated to one app in a showroom, iOS features such as Guided Access keep it locked to that app. The React Native development page covers the sales apps this work comes from.

Every build goes to TestFlight before the App Store. Your team installs it on their own iPhones and iPads, uses it for real and reports problems, and external testers can be invited after Apple's beta review. That is where most issues are caught, while they are inexpensive to fix.

App Review then checks the app against Apple's guidelines. The usual rejections are avoidable: a demo login the reviewer can use, a privacy policy that matches what the app does, no placeholder content or broken links, and payments for digital goods going through Apple's in-app purchase where the rules require it. Releases can also be phased, so an update reaches users gradually and a problem can be paused before it reaches everyone.

Every App Store listing carries privacy details that state what the app collects and why, and they have to match what the app and its third-party tools actually do. Analytics and advertising SDKs count, so they are listed before submission rather than discovered by a reviewer. The same thinking applies to the UAE PDPL: collect what the app needs and say so plainly.

Permissions are asked for in context. A request for notifications on first launch is usually refused; the same request after a buyer saves a property, explaining that they will hear about price changes, usually is not. Tracking users across other companies' apps and websites requires Apple's App Tracking Transparency prompt, and many people decline it, so app campaigns are measured with that in mind rather than with numbers that assume everyone said yes.

React Native is not the right tool for every iPhone app, and the honest answer matters more than the booking. A native Swift build is the better call when the app is built around Apple hardware or frameworks: augmented reality with ARKit, heavy real-time graphics or video processing, deep Apple Watch, widget or CarPlay work, or a feature that depends on an Apple framework released this year. It is also the better call when the app will only ever be on iPhone and you already have, or plan to hire, an iOS team that works in Swift.

In those cases I will say so before we start and recommend you hire a Swift developer for the app. I can still own the parts around it that I do build: the app back end, the tracking, the App Store listing and the campaign that sends people to download it.

Push notifications go through Apple's notification service, usually via Firebase Cloud Messaging or Expo, from an app back end that decides who receives what. Fewer, relevant messages keep people from switching notifications off: a viewing reminder, a price change on a saved unit, a launch they registered for.

The App Store listing is a conversion page. The name, subtitle, keywords, screenshots and the first lines of the description decide most installs, and App Store Connect can produce campaign links so you can see which campaign brought each download. Leads from the app reach your CRM with their source, the same as a web enquiry. The Android side is on the Android app developer page.