Service · Bespoke software

Mobile apps

Engineers at a lift maintenance firm in Malaga call at ten or twelve buildings a day. At each one they log their arrival, complete the inspection, photograph the plate in the machine room and get the residents' association chair to sign. Half those machine rooms sit on rooftops or in basements with no coverage. On paper, reports reach the office three days late; in a web form, they vanish the moment the signal drops. This is exactly where a native app earns its keep: daily use, camera, location and offline working. If your situation is different, say customers who log in twice a year to download an invoice, we will point you to a mobile-friendly website and save you the cost of an app.

2 platforms
iOS and Android, phone and tablet
Offline
syncs once signal returns
Camera and GPS
photos, barcodes, location
Your accounts
on the App Store and Google Play

What falls within the scope of this service

An app is more than what shows on the phone. Behind it sit a server, links to your other software and an update schedule that carries on long after launch day.

Pin down the details with one of our engineers

Cross-platform or native

Flutter or React Native give you one codebase for iOS and Android and a smaller bill. Swift and Kotlin are kept for apps that push the hardware hard, such as continuous camera scanning or Bluetooth links to external devices.

Designed for outdoors

Large buttons that work with gloves on, enough contrast in bright sunshine, screen reader support and scalable text, benchmarked against WCAG 2.1 AA and with Spain's Ley 11/2023 in mind if the service faces the public.

Working without coverage

Entries are stored on the handset and sent automatically when the network comes back. We agree in writing what happens when two people edit the same record while offline.

Server and integrations

An API in data centres in Spain or elsewhere in the EU that holds the data and matches it against your ERP, CRM or management software, so the app does not become one more island of information.

Sign-in and payments

Entra ID for staff already on Microsoft 365; Apple or Google sign-in for customers. If the app charges for real-world services, we wire up Redsys for cards and Bizum, or Stripe or PayPal, within each store's rules.

Sensible notifications

Alerts filtered by role, area or job status. An app that pings too often ends up muted or deleted.

Store publishing

Listings, screenshots, privacy labels and replies to Apple and Google reviewers, always from your company's own accounts.

How the engagement unfolds, one stage at a time

Build effort depends on how many screens and integrations there are. Store review adds a few days nobody controls, so we build them into the plan.

01

Observation

We shadow a working day over video or interview the future users. We look at what happens on foot, what happens at a desk and what never needed a phone at all.

02

Field trial

A prototype installed through TestFlight or Google Play internal testing and used by two or three people in real conditions.

03

Test builds

Regular drops the team installs and uses on the job; bugs get reported from inside the app itself.

04

Launch and lifecycle

Store release plus an update plan for each new version of iOS and Android.

Open the developer accounts in your company's name from day one. Apple requires a D-U-N-S number for organisation accounts and getting one can take a while. If the app goes out under the supplier's account to save time, the ratings, downloads and even the store listing name stay with them. Winning those back later is slow and sometimes impossible.

Common questions

Ask three questions. Will people use it every day? Do they need the camera, location or sensors? Do they work where there is no signal? If all three answers are no, a mobile-friendly website will be cheaper to build and to run, and no app store gets a say.

Article 90 of Spain's LOPDGDD allows geolocation at work as long as staff have first been told in an express, clear and unambiguous way. In the app we restrict tracking to working hours and one stated purpose, show it on screen and keep the data for as short a time as possible. Informing employees, the record of processing and any impact assessment are for your company and your DPO.

Yes, that is a common feature. The app can record clock-in and clock-out with date, time and, if you choose, location, and pass them to your payroll software or to Factorial. How the register is designed and how long it is kept must match employment law and whatever has been agreed with staff.

Apple and Google ship new versions every year and change their rules. At the very least the app needs reviewing, libraries updating and a new release several times a year. This is charged at €75 per hour + VAT, or through a monthly allowance if you also want to keep adding features.

For public administration services, sign-in with Cl@ve or an FNMT digital certificate is feasible, and we integrate it according to that system's technical requirements. For private businesses we use dedicated accounts with two-factor authentication where the risk calls for it.

Let's talk about your app

Explain who will use it, where and how often. We will tell you honestly whether an app makes sense or whether a cheaper mobile website would do.

Hours
Monday to Friday, 9:00-18:00 Spanish time (CET), answers within a working day
Meetings
Video calls via Google Meet or Teams

This site only stores the cookies it needs to work and to remember your chosen city. No advertising or tracking cookies are set. See our privacy policy for the details.