Area 03 — Mobile apps · Spain

We develop apps for iOS and Android — from the idea to the App Store and Google Play.

Every project is run individually: native development in Swift and Kotlin, cross-platform where it is justified, store publication and ongoing support. We build the complex parts: an offline mode for field teams, ERP integrations, payments, geolocation, AI inside the app. A plan with a price within one working day.

Get a plan & price Deep-dive: mobile apps
Swift · Kotlin native + cross-platform
90% < 24 h App Store review — Apple’s data
TestFlight · Play beta on your phone before launch
ES·RU·EN apps in three languages

What we do

For customers and for teams · an engineering approach
How an app is born

Idea → engineering → stores

We start with the task: who the user is, what they do on the move and which systems the app has to talk to. Then come a prototype, native or cross-platform code, integrations and publication. Within the first few weeks you hold a working build on your own phone — TestFlight and a closed Google Play track.

iOS · SwiftAndroid · KotlinCross-platform: Flutter · KMPApps for customers and teamsApp Store / Google Play release
APPROACH

Native where you need full speed and the platforms’ newest capabilities; cross-platform when timeline and budget matter more. The technology choice is part of the service: we explain it with numbers, not tastes.

ATTENTION

The project is run by the engineer who builds it. A demo every week; the first build lands on your phone, not in a slide deck.

IDEA user · scenariosprocesses · systems ENGINEERING prototype · Swift/Kotlinintegrations · tests STORES App Store · Google PlayTestFlight · updates

Complex technical solutions

What separates a tool from “an icon” · 01—09
Solution 01 · offline

Offline mode for field teams

Your technicians work where there is no signal. So does the app: data is stored and synced when the network returns.

What’s included
  • Work orders, photos, client signature — offline — nothing gets lost
  • A sync queue — no conflicts or duplicates when the signal returns
  • Works in a basement, on the road, in the mountains — tested in real field conditions
estimate & timeline — in the 1-day plan
construction · service · deliveryMobile apps →
Solution 02 · integrations

Wired to your ERP and CRM

The work order, signature and receipt photo reach your back office within the minute — no manual re-entry.

What’s included
  • Holded, Odoo, Sage, your own system — via API, both ways
  • Orders, statuses, stock — the phone and the office see the same thing
  • A PDF work order to the client’s email — right after the on-screen signature
estimate & timeline — in the 1-day plan
zero manual entryAPI & integrations →
Solution 03 · payments

Payments and subscriptions

One-tap payment — Apple Pay, Google Pay, card — and subscriptions that pass store review first time.

What’s included
  • Apple Pay · Google Pay · Stripe — the payment methods people expect
  • Subscriptions: StoreKit 2, Play Billing — by the stores’ rules
  • Fees and requirements planned for up front — no surprises at review
estimate & timeline — in the 1-day plan
sales · subscriptionsGet the plan →
Solution 04 · geolocation

Geolocation and tracking

Every van and every call-out on the map; the client sees “your technician is on the way” via a link.

What’s included
  • Routes and service areas — call-outs planned on the map
  • Background tracking — gentle on the battery, with consents handled properly
  • A tracking link for the client — fewer “where are you?” calls
estimate & timeline — in the 1-day plan
delivery · call-outsGet the plan →
Solution 05 · scanning

Scanning and the camera

An employee’s phone instead of dedicated hardware: barcodes, QR codes and documents — with the camera.

What’s included
  • Warehouse and stocktaking — scanning with a phone, no dedicated terminals
  • Documents: photo → data — with AI recognition and human review
  • Labels, expiry dates, traceability — batches and movement history
estimate & timeline — in the 1-day plan
warehouse · retailGet the plan →
Solution 06 · AI

AI inside the app

An assistant and recognition right in the app: on-device — offline and private — or through a protected backend.

What’s included
  • On-device models — Apple Foundation Models, Gemini Nano: no internet needed
  • Claude / GPT through your backend — the keys never reach the client
  • Document and voice recognition — the camera and microphone as tools
together with area 01
support · processesAI integration →
Solution 07 · push

Push and deep links

The notification leads not “to the app” but to the exact screen — the order, the invoice or the alert.

What’s included
  • Scenarios, not broadcasts — order status, a reminder, an abandoned basket
  • Deep links — from the notification straight to the exact screen
  • Frequency and consents under control — no spam, no opt-outs
estimate & timeline — in the 1-day plan
bringing customers backGet the plan →
Solution 08 · BLE / IoT

Bluetooth and equipment

The app talks to your equipment directly: configuring a sensor — without a laptop and without the internet.

What’s included
  • BLE connection — sensors, locks, scales, machinery
  • Reconnection in field conditions — resilient to interference
  • Readings in real time — right on the technician’s screen
estimate & timeline — in the 1-day plan
manufacturing · IoTGet the plan →
Solution 09 · for teams

An internal app (MDM)

Two apps from one project: the customer app in the stores, the internal one for staff — outside the stores, via MDM.

What’s included
  • Distribution via MDM — no publication, no review
  • Biometric sign-in — Face ID / fingerprint, protected storage
  • Work orders, warehouse, time tracking — Spain’s statutory registro horario
estimate & timeline — in the 1-day plan
internal appsGet the plan →

Attention to every project

Individual · no production line
Rule 01

You talk to the engineer

The project is run by the person who builds it: no messages garbled on the way through account managers. Communication in Spanish, Russian or English.

One contact for the whole project
Rule 02

Stages and price — in the contract

The plan splits the project into stages, each with a fixed price. You pay per stage, for accepted work — not everything up front.

A fixed price, not a rough guess
Rule 03

The build on your phone

The first working build reaches you via TestFlight and a closed Google Play track within the first few weeks. You hold the app in your hands long before launch.

A demo every week
Rule 04

Everything is yours

Developer accounts, code, certificates and access are registered to your company from day one. Support can be switched off — the app keeps working.

No ties to the studio

Platform standards — by the official guidelines

Apple · Google · EU law
Apple · HIG

Design to the Human Interface Guidelines

We design to Apple’s official guidelines — including the new Liquid Glass design system (iOS 26). The app looks and behaves like a native part of the iPhone.

Native behaviour on iOS
Google · Material 3

Material 3 Expressive for Android

An interface built to Google’s current design system: dynamic themes, lively animations, familiar Android gestures. Not “an iOS layout stretched over Android”.

Native behaviour on Android
Stores · publication

Turnkey publication

Privacy labels and App Tracking Transparency for the App Store, Data safety and target API 36 for Google Play (a 2026 requirement). We prepare the build to pass review first time.

90% of reviews < 24 h — Apple’s data
Google · vitals

Stability to the stores’ thresholds

Crashes < 1.09% and freezes < 0.47% — the Android vitals thresholds beyond which Google reduces an app’s visibility. We monitor them from day one, not after complaints come in.

Stability = store visibility
EU law

GDPR · DSA · accessibility

GDPR consents, DSA trader status for publishing in the EU and the EAA accessibility requirements — in force since 28 June 2025 and applicable to apps as well. The paperwork is part of the project.

EU publication without surprises
Security

Security by architecture

Biometrics, Secure Enclave and Keystore, data encrypted on the device and in transit; AI and payment keys live only on the backend — never in the client.

Face ID · Keystore · encryption

How we run the project

A build on the phone before the slide decks
01

Review

Task, users, processes, systems. Free, one call.

02

Plan with a price

Stages, timelines, technology (native / cross-platform) and a fixed price — within one working day.

03

Prototype

A clickable prototype: user journeys are tested before any code.

04

Sprint builds

The first build in TestFlight and a closed Google Play track within the first few weeks.

05

Release and support

Store review, crash and vitals monitoring, updates under an SLA.

Questions asked before starting

Price · technology · timelines · stores
How much does an app cost, and what does the price depend on?+
The price is calculated per project and fixed per stage in the contract. What matters: one platform or two, the amount of offline logic, integrations with your systems, payments, AI features. The sensible path is to start with an MVP: one key feature taken all the way to the store. A plan with an exact price is prepared within one working day, free of charge.
Native or cross-platform — which should we choose?+
A decision we make together, with numbers, and it is part of the plan. Native (Swift/Kotlin) — when you need full speed, Bluetooth/sensors and the platforms’ newest capabilities on release day. Cross-platform (Flutter, Kotlin Multiplatform) — when timeline and budget matter more: shared logic is written once; the shared-logic approach is officially backed by Google itself.
How long until publication?+
The clickable prototype — within the first two weeks. The first working build in TestFlight — within the first few weeks of the project. An MVP — usually 8–12 weeks, per the stages of the plan. Apple’s review, according to Apple’s own data, takes under 24 hours for 90% of submissions — but we always leave a margin for a first release.
What is needed to publish in the stores?+
Developer accounts — Apple ($99/year) and Google Play ($25 one-off), registered to your company. Then: privacy labels and App Tracking Transparency for the App Store, Data safety for Google Play and, for the EU, trader status under the DSA. All of the paperwork is part of the project; you only confirm your company details.
The app is only for our staff. Do we have to publish it in the stores?+
No. Internal apps — work orders, warehouse, time tracking — are distributed via corporate MDM, bypassing the public stores and their reviews. It is faster, and it keeps your working tool away from competitors.
Who owns the app?+
You do. Developer accounts, code, certificates, access and data are registered to your company from day one. Support is optional: switch it off and the app keeps working, and we hand everything over to your specialist.
What happens after release?+
We monitor crashes and the vitals thresholds (Google Play visibility depends on them), update the app for new iOS and Android versions — store requirements rise every year — and develop features based on usage numbers. SLA support is a subscription you can stop.

Describe the task — you’ll get a plan and a price within one working day, and you’ll see the first build on your own phone.

Get a plan & price Message us on WhatsApp
Free review · No obligation · ES / RU / EN · GDPR