Development 02 / 04
iOS apps for iPhone and iPad
Use
When a native app makes sense
- The work happens on the move, sometimes without a reliable connection.
- The camera, location or other device features are part of the workflow.
- Your users expect to find the application in the App Store.
- Notifications and returning to the app quickly matter.
Scope
What is included
- Concept
- Which tasks belong in the app, and which stay in the browser or the backend?
- Design
- Interaction that follows iOS conventions, including accessibility and dynamic type.
- Development
- Native implementation, data storage and the connection to your backend or web app.
- Release
- Preparation for App Store Connect, a test phase and submission for review by Apple.
Practice
From our practice
We have built iOS apps of our own in the past and know the route through App Store Connect and Apple’s review. Our four current products run in the browser today; where native apps have been announced, they are not yet available.
Framework
What shapes a quote
- Whether only iPhone or iPad as well should be supported.
- Offline capability and synchronisation with a backend.
- Device features such as the camera, location or notifications.
- Maintenance after launch, especially for new iOS versions.
FAQ
Frequently asked questions
Do you also build for Android?
Our focus for native apps is iOS. If Android matters, we discuss whether a web app or another approach fits better.
Who publishes the app?
Usually the app is released under your company’s Apple developer account. We help with setup, submission and questions raised during review.
Can you guarantee App Store approval?
No. The review is up to Apple. We prepare the app carefully according to the current guidelines and respond to feedback.
Other focus areas
Next step
Tell us what you are planning.
A few sentences about your goal, users and starting point are enough. We reply by email and suggest a sensible next step.