Which mapping stack do you usually choose?
That depends on the use case. For consumer and public-facing apps, we often work with Mapbox GL or Maptiler because of their attractive vector styling and reasonable licence costs. For public sector projects, we usually choose Leaflet on top of OpenStreetMap or a combination with PDOK tiles, because that is licence-free and interoperable. For organisations that have already invested heavily in ESRI, we connect to ArcGIS Online or ArcGIS Enterprise. We use Google Maps where recognisability matters more than customisation. We always advise based on your data, target audience and existing contracts, not on what we happen to be used to.
How accurate is the location in the app?
With the standard GPS chip in modern smartphones, you typically get three to five metres of accuracy in the open air, slightly less in urban areas. For field surveys, archaeology or cable and pipeline work, that is sometimes not enough, so we connect external GNSS receivers such as the Trimble Catalyst, Emlid Reach or a Septentrio Mosaic via Bluetooth. With RTK correction via an NTRIP stream, you can then achieve centimetre-level precision. The app automatically falls back to the built-in GPS if the external receiver is not available.
Does the app really work offline in an area without a network?
Yes, and for most of the geo apps we build it is a core requirement. We download tiles and feature data to the device in advance, store all work orders, photos and measurements locally in an SQLite or MMKV store, and synchronise via a queue as soon as the network is back. Conflict resolution for objects touched by several field workers at the same time is part of the design by default. We test this in every sprint in airplane mode and on poor 4G, not just on fast office Wi-Fi.
Can you integrate with our GIS environment?
In practice, almost always. For Esri: ArcGIS Online via REST services, or ArcGIS Enterprise. For open-source stacks: GeoServer with WMS, WFS or WMTS, or a direct PostGIS database. For QGIS publications: an intermediate step via a WFS feed or an exported GeoPackage. For PDOK data: the open WMS and WFS services. We build two-way integrations where that makes sense, so field captures land automatically in your office GIS and vice versa.
What about GDPR when it comes to people's location data?
A person's location is classed as special-category personal data under the GDPR, especially when it is collected continuously or in real time. We build consent flows, data minimisation and retention periods directly into the app, with an audit log of when and why location is collected. For fleet applications with vehicles assigned to individuals, we work with works council agreements and privacy-by-design principles. For projects involving the location of patients, pupils or residents, we carry out a DPIA as standard. We work with your privacy officer or DPO to get the legal details right.
How do you combine a geo app with AI or image recognition?
Organisations increasingly want a photo taken in the field to be categorised or analysed automatically: an ecologist photographs a plant and instantly gets the species back, an inspector registers waste and has the type detected automatically, a property valuer photographs damage and receives a first estimate. We build this as a separate AI layer on top of the geo app, with models running on-device or in the cloud depending on privacy and data volume. For our approach and the possibilities, see our page on
AI development.
What is INSPIRE, and do we need to comply with it?
INSPIRE is a European directive that requires public-sector organisations to publish certain spatial datasets in a standardised format with standardised metadata. If you are a municipality, water board, province or regional environmental agency working with public spatial data, it generally applies to you. We make sure your app's data export produces the right GML or GeoJSON formats, with metadata in the ISO 19115 format. INSPIRE usually does not apply to private parties, but interoperability with PDOK datasets is often still desirable.
Can you do indoor positioning without GPS?
Yes. We place Bluetooth beacons (from vendors such as Estimote or Kontakt.io) at fixed positions, and triangulation gives a position accurate to within a few metres. For larger buildings we use Wi-Fi fingerprinting on top of existing access points. For BIM-driven routing, we load an IFC model into the app, so users can navigate through a 3D representation of the building. Indoor positioning works best for organisations with fixed physical infrastructure: warehouses, hospitals, stadiums, car parks.
Native or cross-platform?
For geo apps we usually choose Flutter or React Native, because the mapping libraries (Mapbox GL Native, MapLibre, Leaflet via webview) work comparably on both platforms and you keep a single codebase. For projects with very heavy graphics requirements or very specific hardware integrations, such as deep integration with an external GNSS receiver via a proprietary SDK, we sometimes choose native iOS (Swift with MapKit/CoreLocation) and native Android (Kotlin with the Maps SDK). During discovery we discuss what fits your requirements and existing engineering capacity.
Who manages tile licences and hosting costs?
That is part of the maintenance contract if you take one out. Mapbox, Maptiler and Google Maps use a usage-based model (per map load or per tile request), whereas ESRI works with named users. We monitor usage, scale the plan up or down, and give you monthly insight. For public-sector projects we use PDOK tiles wherever possible because they are licence-free, with a commercial provider as a fallback for specific styles or regions.
Do you also work with our own GIS analysts or developers?
Yes, on geo projects that is the rule rather than the exception. Many clients have a GIS team that handles the data layer and analyses, while we build the mobile layer and, where needed, the APIs in between. We work in the same Git repository, align with your projections and data models, and do pair programming where it speeds up knowledge transfer. By the end of the project, your own team can maintain the codebase completely independently, with no lock-in to us as a supplier.