What Our iOS App Development Includes
- screen design that follows Apple's Human Interface Guidelines;
- Swift development with SwiftUI for most screens and UIKit where precise control is needed;
- device features: Apple Pay, Sign in with Apple, Face ID or Touch ID, camera, location, widgets and notifications;
- a backend, API and admin panel, or a connection to the ones you already have;
- offline behavior: what to show without internet and how to save user actions and send them later;
- integrations with your CRM, accounting system, payment provider and shipping carriers;
- TestFlight builds after every sprint, testing and App Store submission.
Not every project needs all of these. We add only what serves your business goal, because every feature is extra code you maintain for years.
When Native iOS Is the Right Choice, and When It Isn't
Native development is worth it when the app is your product, when it works deeply with iPhone features or when interface quality directly drives sales. We recommend something else if:
- iPhone and Android users matter equally to you and the features are standard (catalog, account, orders), in which case a single Flutter or React Native codebase costs less to build and maintain;
- most of your customers use Android, so it makes more sense to start with an Android version;
- you only need to validate an idea, and an app store install isn't critical, in which case a progressive web app may be enough.
Keep in mind that native iOS covers one platform only. Android needs a separate app, effectively a second project. Apple also reviews every version manually, so we build review time into your release plan.
New App or Improving an Existing One
A new app starts with a list of user scenarios: what a person does in the first minute after installing, what they do daily and what they do once a year. The first version includes only the key scenarios, so you reach the App Store sooner and see how real users behave.
An existing app gets an audit first: what language it is written in (some older projects are still in Objective-C), which libraries are outdated and where it crashes. Then we propose a plan of what to fix right away and what to rewrite gradually, without pausing your update releases. Objective-C code can be maintained as is while new parts are written in Swift.
App Store Publishing
We recommend registering the Apple Developer account in your company's name, so the app and all its reviews belong to you. For review, we prepare screenshots, the description, data collection disclosures and test access for the Apple reviewer. Most rejections come from crashes during review, incomplete disclosures, missing test access or selling digital goods outside Apple's payment system, and we check all of these before submission.
What We Need From You
- A description of who will use the app and what they should be able to do.
- Documentation or access to the systems the app connects to, if any.
- Brand materials, if you have them.
- An Apple Developer account in your company's name.
What Affects Development Cost
- Number and complexity of screens: standard lists and forms, or custom animations and non-standard elements.
- Backend: whether there is a ready API or it needs to be built along with an admin panel.
- Device features: payments, camera, background location, widgets, offline mode.
- Platforms: iPhone only or iPad too, and whether you need an Android version in parallel.
- State of the existing code, for improvements: the language, the age of libraries, and whether there are tests and documentation.
We provide an estimate after reviewing your project: we break it into phases and explain what each one includes.
Frequently asked questions
Can we start with iOS and add Android later? Yes, that's a common path. The backend, design and logic are already worked out, so the second platform usually takes less work than the first.
Will an iPhone app work on iPad? It will, but it will look like an enlarged phone. If people use tablets often, it's better to adapt the interface for the larger screen.
Why might Apple reject an app? Most often because of crashes during review, incomplete data collection disclosures, missing test access, or selling digital goods outside Apple's payment system.
Do you work with older Objective-C apps? Yes. That code can be maintained as is, while new parts are written in Swift. Both languages work in the same project.
Can you build the backend too? Yes. We can connect to your existing API or build the backend along with an admin panel.
Will you maintain the app after launch? Yes, through our app support and ongoing development service: crash monitoring, dependency updates and new features.
Why Promodex
Mobile apps are one of Promodex's core areas, alongside websites, among 750+ projects delivered since 2015. Our portfolio includes Yerevan Mall, MyAmeria, Telcell Wallet and Kinodaran. Designers and developers are an in-house team, and we never outsource the work. After your App Store launch, we stay with you, updating the app for each new iOS version and growing it alongside your business.