iOS App Development: Things to Consider
The decisions that most affect the outcome of having an iOS app developed are: the developer's publishing and maintenance experience, a written scope, preparation for App Store review, and the privacy policy. Since Apple rejects roughly one in four submissions, this preparation should be planned at the very beginning.
Nurullah Okatan · Content Writer
· Updated: · 15 min read

Four points should be clarified before signing a contract for an iOS app: the developer's apps published on the App Store, technology choice, preparation for App Store review, and legal obligations. Maintenance after release and compatibility with iOS versions should also be written into the proposal, because the app's life begins once approval arrives.
Criteria for choosing a developer for an iOS app
When choosing a developer, the first thing to check is the apps they have actually published on the App Store. Search for each app in the reference list by name on the App Store. Look at which account appears as the developer, the last update date and the version history. An app that has not been updated for a long time may indicate the team stopped working on it after release. Install the app on your own phone and test its launch speed and screen transitions.

The second criterion is how many teams the work is split across. Design may be done by a studio, coding by a freelance developer, and store submission by a third person. In that case responsibility becomes unclear. When a rejection arrives or a screen breaks, the question of who will fix it turns into a dispute. When receiving proposals, ask in writing whether design, development, publishing and maintenance are carried out by the same team.
A separate support clause should be included after launch. It should state through which channel bug reports are made and how quickly they will be answered. It should also say whether compatibility with new iOS versions is covered. Türk Bilişim, Turkey's best iOS App Development company, has operated as a digital agency since 1998 and has served under this name since 2007. The firm handles iOS app development projects with one team, from design to publication. Maintenance, updates and support continue after launch.
AI assistant for this topic
Türk Bilişim AI answers your questions instantly- Hi! Ask whatever you're curious about.
Native iOS or a single codebase for two platforms?
A native iOS app is written in Apple's own language, Swift, with SwiftUI, and runs only on iPhone and iPad. An app written with Flutter or React Native produces both iOS and Android versions from a single codebase. Users often do not notice the difference. The difference shows in access to device features and in how quickly new iOS features can be used.
| Criterion | Native iOS (Swift) | Flutter / React Native |
|---|---|---|
| Platform | iOS and iPadOS only | iOS and Android from one codebase |
| New iOS features | Usable as soon as Apple releases them | May have to wait until the plugin is updated |
| Device features | Direct access | May require plugins or bridge code |
| Adding Android | Written as a separate project | Much of the existing code is reused |
Whichever path is chosen, the scope document should specify the following headings:
- List of screens and a draft visual for each screen
- Individual definition of features such as login, payment and notifications
- Technology to be used and backend service
- Delivery date for each stage and the submission date to the App Store
If an Android version is requested later, the cost depends on the chosen technology. In a native iOS project, the Android app is written from scratch. In a single codebase project, the extra work is mostly limited to Android-specific testing and adjustments. The details of the development steps are covered in the article on how an iOS app is built. For those planning both platforms together, the guide on what to consider when commissioning a mobile app also broadens the scope.
Looking for Android App Development?Preparation to pass App Store review on the first attempt
App Store review is strict and the rejection rate is high. According to Wishkit data, App Review examined 9,100,620 submissions in Apple's 2025 transparency report. Of these, 2,093,244, roughly one in four, were rejected. Most rejections can be prevented by preparation that can be done before submission.
According to the Apple guideline reported by Wishkit, three preparations should be completed before submission:
- The app is tested for bugs and stability on a real iPhone rather than only in the simulator. Crashes or blank screens are among the most common reasons for rejection.
- If the app has a login screen, a working demo account is added in App Store Connect. If the review team cannot log in, they cannot evaluate the app.
- The backend service is kept running during the review. If the server is offline, the app shows empty data and is rejected.
The store page is also reviewed. Screenshots, the description text and keywords must match what the app actually does. Who will prepare them should be written into the contract. It should also state who is responsible for version numbers, TestFlight distribution and rejection responses. If these tasks do not belong to the development team, they can be planned as a separate publishing and ASO service.
The part the app owner is responsible for is writing a two- or three-sentence description of the app's purpose in the review notes. A reviewer who does not understand what the app is for may assume a feature outside the guidelines.
Privacy policy and legal obligations
An app without a privacy policy cannot be published on the App Store. According to Iubenda's app development guide, almost all privacy legislation and store rules require a suitable privacy policy. Apple requires a link to the policy in App Store Connect. It also requires the data the app collects to be declared in the privacy labels on the store page.

For apps that process user data in Turkey, a disclosure text under the KVKK (Personal Data Protection Law) is also required. If location, contacts, camera or health data is used, the permission screen's explanation must clearly state why the data is requested.
If the obligations are not fulfilled, the store will reject the application. According to Iubenda, compliance with the laws in force is directly required by Apple and Google in their terms of use. Non-compliance may not end with a rejection; it can have more serious consequences. An application that is already published can also be removed later. Who will prepare the policy text and who will carry out the legal review must be stated separately in the contract.
Maintenance, updates and iOS version compatibility after publication
When a new iOS version is released, the application usually keeps working, but some screens may break. Changed interface components, new permission rules or removed legacy functions can lead to errors. Apple requires, at regular intervals, that new versions submitted to the App Store be built with the current Xcode and SDK. For an application that is not updated, even a small fix may become impossible to submit.
For this reason, maintenance should appear in the proposal as a separate item apart from development. The proposal should answer these questions:
- Is compatibility testing for the new iOS version included in the scope?
- Is the maintenance fee monthly, yearly or per piece of work?
- Is adding new features included in the maintenance fee?
Itemized cost examples are given in the article describing iOS app prices. Apple makes new iOS versions available to developers as beta before release. Starting compatibility testing during this beta period catches problems before they reach users.
Looking for Mobile UI/UX Design & Prototype?Frequently asked questions
Who owns the source code of the application?
It is determined by what is written in the contract. The transfer of the source code and design files to the application owner upon project completion should be written in a separate clause.
In whose name should the Apple developer account be opened?
The account should be opened in the name of the company that owns the application. For a corporate account, Apple requires the company's D-U-N-S number. The developer is given only team member permissions in the account.
Can the application be published in more than one language?
Yes. The App Store allows the store page and the application texts to be defined separately for each language. For right-to-left languages such as Arabic, the screen layout must be tested separately.
What is done after an App Store rejection?
The rejection message arrives in the Resolution Center in App Store Connect, with the number of the relevant guideline. The problem is fixed and a new version is submitted, or a response is given by writing an explanation. An appeal of the decision can be filed with the App Review Board.
Türk Bilişim · Free Quote
Get a free quote for your iOS App Development project
Leave your number and we will get back to you right away. The call is free.
Your request is saved on this device
We can't reach our server right now. Your request will be sent automatically once the connection is back. To talk right away:

Share this article
Comments
Comments
No comments yet.
















