Mobile app development for iOS and Android

It depends mainly on the user roles, the device features, payments, real-time features and integrations. Digitup Studio projects start at €1,000, but an iOS and Android app with a backend and back office costs more than that minimum, because each integration adds work. After a first call, we propose phases, price and payment model: a fixed-scope project, payments spread over 6 or 12 months, or Build & Run.

A first publishable version of an app like 23TopTraining, with plans, sessions, a back office and notifications, usually takes two to four months. If the app has several user roles, payments and real-time features, it may need more phases. Store review comes on top of that: from less than a day to a week or more in exceptional cases. We propose the phases before starting, so you know what each release includes.

For most business apps with payments, maps or notifications, a hybrid app built with Ionic and Angular is enough: one codebase for iOS and Android, so every change is made once. Native (Swift or Kotlin) suits heavy graphics, augmented reality or very specific hardware. Mallorcab, for example, is built with Ionic and Angular and still takes Apple Pay and Google Pay and connects to the taximeter over Bluetooth. Digitup builds hybrid apps; if yours needs native, we'll tell you at the start.

Yes, we handle submission and release, as we did for 23TopTraining. Apple reviews every app and update, and typically handles 90% of submissions in under 48 hours; on Google Play, some reviews take up to seven days, or longer in exceptional cases. If you publish as a company, both stores will ask for a D-U-N-S number. They also require in-app account deletion if your app lets users sign up.

Ideally, the Apple and Google accounts are in your company's name from day one, so the app sits under your brand and you don't depend on any supplier to update it. The code and access are handed over when a fixed-scope project is complete or, with flexible payment, once the payments are complete. Build & Run includes a buyout option defined from the start.

Dependencies and SDK versions need updating when Apple and Google change their requirements, bugs need fixing, the backend needs monitoring and features keep evolving. For example, since 31 August 2026 Google Play requires new apps and updates to target Android 16 (API level 36). Existing apps that still target Android 14 (API level 34) or lower are no longer offered to new users on devices running newer versions of Android.

Yes, when the app needs them, which is usually the case. We build the backend in Node.js with NestJS or in Python with FastAPI, the database and a back office so your team can manage users, content or orders without touching code. If you already have a backend, CRM or ERP, the app connects to it instead of replacing it.

Sometimes. A PWA is a website that users install from the browser, without going through the App Store or Google Play, and it can be enough for internal tools or occasional use. It has limits: on iPhone, its notifications only work from iOS 16.4 onwards and only if the user adds it to the Home Screen. We build PWAs too.

Yes. We join apps that are already live to fix architecture or infrastructure problems, add features or integrate AI, or just to redesign the UX/UI, as we did with the Fonditel app: we started with stakeholder interviews and a Nielsen heuristic analysis and finished with usability tests. If the app is built natively, we'll tell you honestly whether we can take it over or whether another team would be a better fit.

Push notifications, yes: 23TopTraining, for example, announces new sessions and sends reminders to help users stay consistent. Offline, the app can be set up to show content that's already downloaded or to record actions and sync them later. Anything that depends on the server, such as payments, bookings or real-time tracking, needs a connection. It's worth deciding early which screens must work offline, because it affects how data is stored on the phone.