An iOS developer builds your iPhone app in Swift, within Apple's rules and limits

Only if the app, or an SDK inside it, collects data about people and shares it with other companies to track them across apps and websites. Apple then requires the App Tracking Transparency prompt first, and saying no may not cost anyone a feature, content or reward. The developer checks what each SDK does before App Review finds out for you.

You do, as far as Apple is concerned: an app is responsible for all the code its SDKs bring in. So the developer reads each SDK's privacy manifest before adding it, keeps the SDKs Apple lists on signed versions Xcode can verify, and removes the ones the app no longer uses.

Yes, within limits. A widget shows entries from a timeline the app prepares in advance, the app can ask for a reload when its data changes, and WidgetKit push notifications let your server prompt an update. Reloads count against a budget iOS sets to protect battery life, so the developer decides which changes are worth one.

Only in the kinds of app Apple supports there, among them audio, messaging and calling, navigation, EV charging, fuelling, parking, quick food ordering and driving tasks, and only once Apple grants the CarPlay entitlement you request. Where the app qualifies, the developer builds its CarPlay screens from Apple's templates. Widgets and Live Activities can appear in CarPlay without a CarPlay app.

Apple reports that 90% of submissions are reviewed within 24 hours, though each rejection adds a round. The developer reads the guideline the rejection cites, replies in App Store Connect when the reviewer has missed something, and changes the build only when the rule applies. Expedited review is meant for critical bug fixes, so release dates are planned without it.

SwiftUI for most new screens, UIKit where it still does a job better, such as some complex lists, rich text editing or a custom camera view. The two run side by side in one app, so nothing has to be rewritten to start. Your minimum iOS version matters too, because newer SwiftUI features need newer iOS versions.

The iPad version, usually yes: it is the same app, with layouts that adapt to larger screens, Split View and Stage Manager. An Apple Watch app is a separate target with its own interface, its own data sync with the phone and tight limits on battery and background time, so it is scoped and estimated as separate work. The profiles we send say which of the two a developer has shipped.

Yes. Swift and Objective-C compile into the same app through a bridging header, so nothing has to be rewritten before work starts. Objective-C is replaced file by file as features change, starting with the code that changes most often, and left alone where it is stable and rarely touched. A full rewrite is seldom worth what it costs, and we will say so.

Yes. Many clients start with one senior engineer to cover a specific capability or capacity gap, then add specialists only when the roadmap requires them.

Yes. Adding an engineer follows the same route as the first, and you interview them. Reducing the team follows the notice period agreed in the contract, and the work is handed over in your repository before anyone leaves.

Yes. You manage priorities and day-to-day work directly, in your own channels and delivery process.

Yes. You interview every candidate using your own process and make the final decision about who joins the team.

Our engineers are ImproveIT employees and long-term contractors working through our teams in Poland and Ukraine. We are not a freelance marketplace and do not resell developers from other vendors.

Replacement terms are defined in the contract upfront, so it does not become a negotiation.

You do. IP assignment is included in the contract, and we can sign an NDA before discussing the project.

We sign an NDA before discussing the project, and confidentiality and IP assignment are part of the contract. Engineers work in your repositories, cloud accounts and tools with the access your team grants, so you can narrow or revoke it at any time.

Yes. Our engineers work with teams across Europe and the US. We agree the required working-hour overlap before matching candidates.

Our developers work in English with international product and engineering teams every day. English level is included in the candidate information you receive before the interview.

Rates depend on the role, seniority, experience, and engagement model. You receive the rate, availability, and candidate profile in writing before making any commitment.

Both are agreed before the engagement starts and included in the proposal and contract. We are flexible in that and usually agree on the terms suitable for a client.