Service · App development

Custom survey app development.

A custom app for pulse surveys, NPS measurement, market research, patient PROMs or panel research. Use it when SurveyMonkey or Typeform fall short, for example because you want to own your data, because it needs to work offline, or because your routing logic is too complex for a SaaS template. We build it to measure, native for iOS and Android, GDPR-compliant and connected to your own analytics layer.

Offline modeBranching logicGDPR-compliantReal-time analytics

A survey app is more than a digital questionnaire.

The average survey tool, whether SurveyMonkey, Typeform, Microsoft Forms, Google Forms, Qualtrics or one of the dozens of variations, is fine for a one-off study with thirty respondents and a few simple questions. But once the work grows, the target group changes, or the answers need to land somewhere other than an Excel export, those tools reach their limits. A serious survey app does more: it goes into the field, works without a network connection, adapts based on what the respondent has already answered, and sends the data directly to your own warehouse or CRM instead of the vendor's account.

We have been building survey apps for years for organisations that find their research question doesn't fit a SaaS template. Healthcare researchers who need to administer patient PROM questionnaires on a tablet at the bedside, with encrypted storage and integration with the EHR. HR departments that want to run a monthly pulse survey among thousands of employees without the data leaving the premises. Marketers who want to build a panel with deeper segmentation than a SaaS provider offers. Research agencies running field research where interviewers go out on the street with a tablet and only have a connection in the evening.

In between sits the organisation that could get by with Typeform or SurveyMonkey, but faces one of three problems a standard package cannot solve: their routing logic is too complex (for example, a patient PROM with conditional skips based on earlier answers plus a previous measurement), their answers must be exported in a custom format for a specific integration, or they simply do not want their respondent data stored on a server in the United States. For those scenarios, custom software pays off, because the flexibility and data ownership gained quickly recover the extra investment.

A custom survey app adapts to you, not the other way round. Together we map out which questions are asked, to whom, in what context, and what follow-up or aftercare is attached. On that basis we design an app that gives respondents a pleasant experience, because low drop-out is exactly what your research or pulse measurement depends on, and that gives you, as the client, full control over the data, the schedule and further development. If you first want a broader orientation on what a custom app involves, see our page on app development for the general approach.

Three types of survey app we often build.

Depending on who needs to respond, in what context and what needs to happen with the data, the approach differs. In the first conversation we advise which format suits your research.

Compact project · fixed sprint budget

Pulse and NPS app for internal measurements

For HR and customer success teams: short questionnaires repeated regularly with the same group. Employee pulse, customer NPS, pupil evaluation or supplier satisfaction. Push reminders at agreed intervals, anonymisation where needed, and a dashboard in which trends by team or segment are visible at a glance. Often connected to an HRIS or CRM so that respondent segmentation is automatically correct.

Push remindersAnonymisationTrend dashboardHRIS or CRM integration
Mid-sized project · fixed sprint budget

Field research with offline mode

For market researchers, panel research agencies, event organisers and inspectors who conduct surveys on location. A fully offline app running on a tablet or phone: interviewers administer questionnaires in shopping centres, at events, in deprived neighbourhoods or in care facilities without wifi, and answers sync as soon as a connection is restored. Includes photo and video questions, geolocation capture and interviewer instructions within the same flow.

Offline-firstPhoto and video questionsGeolocationInterviewer mode
Larger project · fixed sprint budget

Patient PROM, academic and panel research platform

A more complex platform for longitudinal research with multiple measurement moments per respondent, intricate branching logic and sensitive data. Patient Reported Outcome Measures in healthcare with EHR integration, longitudinal panel research with respondent incentives, or academic research with REDCap export. Includes an informed consent flow, role-based dashboards for researchers and optional end-to-end encryption at respondent level.

Informed consentMulti-wave designREDCap exportNEN 7510-proof

What a custom survey app can do as standard.

The technical building blocks that appear in virtually every survey app, however different the content of the research. We build this layer afresh each time, tailored to your questionnaire, target group and compliance context.

  • Branching logic and conditional skipsHide, show or reword questions based on earlier answers, demographics or an earlier measurement wave. Far beyond the often restrictive if-then skip logic of standard packages, including score-based routing and behavioural logic.
  • Offline mode that causes no drop-outRespondents and interviewers can work entirely without a network. Answers, photos, video and signatures are stored locally in encrypted form and sync automatically once a connection is restored. No lost responses.
  • Multi-language and regional variantsQuestionnaires in several languages, with accurate translations of scale items (a 5-point Likert scale in Polish uses different wording from Dutch) and regional formats for dates, currency and addresses.
  • Multi-modal question typesIn addition to text and multiple choice: photo uploads, video questions, audio recordings, slider scales, drag-and-drop ranking, map input for geolocation and hand-drawn inputs. For when a question genuinely asks for something different from a radio button.
  • Push reminders and reminder cadenceTargeted push notifications at agreed moments, with decreasing frequency for non-responders and personalised reminder text based on the respondent's relationship to you.
  • Real-time analytics and exportsA dashboard where researchers, HR managers or customer success teams can watch a wave progress live, with segmentation by department, region or cohort. Plus direct export to SPSS, R, Python notebooks, BI tools or your own analytics platform.
  • GDPR consent flow and data minimisationInformed consent screens with granular permission per data category, the option to withdraw consent afterwards, retention policies per field, and pseudonymisation or anonymisation on export. GDPR-compliant by design, not bolted on afterwards.
  • Native iOS and AndroidWe usually build in Flutter or React Native so a single codebase runs on both platforms, with native performance for camera, GPS, offline storage and push notifications. Pure native iOS or Android development is also an option where requirements call for it, for example when integrating with biometric hardware.
  • Integrations with your own systemsIntegrations with HRIS tools (AFAS, Visma, Personio), CRM systems (HubSpot, Salesforce, Microsoft Dynamics), marketing automation (Marketo, ActiveCampaign), healthcare platforms (HiX, ChipSoft, REDCap) and BI warehouses (Snowflake, BigQuery, Azure Synapse). No more manual exports.
  • End-to-end encryption (optional)For research involving highly sensitive data, such as psychiatric measurements, victim surveys or whistleblower reports, key management at respondent level so that even our backend cannot read the content. Includes an audit log for data access.
  • Maintenance contract (optional)Ongoing maintenance, OS updates, security patches and further development for a fixed monthly fee. Includes monitoring, backups and a dedicated contact for researchers who want to set up new waves.

When custom development beats SurveyMonkey or Typeform.

Not every study needs its own app. For a one-off short questionnaire, the familiar SaaS tools are perfectly adequate. Here are six signals that prompt our clients to move to custom development.

Data ownership

Data must not leave the building

For research in healthcare, government or HR contexts involving personal data, you may not want respondent data stored on the servers of a US SaaS provider. A custom app on your own infrastructure or a European cloud solves this in one go, including clear data location agreements that you can point to in discussions with the data protection authority.

Fieldwork

No network at the location

Your interviewers administer questionnaires in a care facility with poor wifi, out in a polder, at an event in a large hall, or during a sample survey at respondents' homes. SaaS tools perform poorly or not at all offline, and you lose responses the moment the connection drops. An offline-first app handles that entirely.

Complexity

Routing too complex for the standard

Your questionnaire uses routing based on earlier answers, scores from a previous wave, demographics and behavioural data from a connected system. SaaS tools offer if-then skips on a single answer but fall short on multi-factor logic or cross-wave routing. Custom software lets you model that routing exactly as your research design requires.

Integration

The answers must go somewhere specific

You no longer need to manually load Excel exports into a data warehouse or import them into a CRM. The answers should land directly in HubSpot, Salesforce, Marketo or your own data pipeline, with the right fields and transformations. SaaS integrations are often generic and call for custom middleware. That custom app already includes this layer.

Scale

The same study, over and over again

You carry out a fixed measurement monthly, quarterly, or with every new employee, customer, or patient. SaaS tools make you set up the questionnaire and export the data again each time; a custom app automates that rhythm completely and builds up a longitudinal dataset that you can analyse for years to come.

Branding

The respondent should feel that this is your research

Whether the respondent is a customer, employee, patient, or panel participant, the app is the face of your research to them. A SaaS template with a vendor logo at the bottom gives a different impression from an app in your own corporate identity, with your own welcome text and the right tone of voice. That demonstrably makes a difference to response rates.

Not yet sure about a large project?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.

Explore OneDayBuild →

How a survey app project runs.

1

Introduction and research question scan

A conversation in which we map out your research goal: who your respondents are, how often you measure, which questions are asked, what compliance applies, and what needs to happen with the data on the other side. We immediately establish what a standard package can do and where custom development pays off, honestly, including if the outcome is that Typeform is perfectly adequate for your case.

2

Questionnaire design and wireframes

Together with you and, where relevant, a methodologist, we design the respondent flow: what the opening text is, what the logical order of questions is, where the risk of drop-out lies, and what the informed consent flow looks like. We test wireframes with two or three end users before writing a single line of code, because low drop-out starts with a pleasant first impression.

3

Building in sprints

Every two weeks we deliver a working version of the app on your tablets and phones. You test it, a small pilot group of real respondents tests it, and we adjust continuously. A first working version is ready after a few sprints, and a production app after a project of several sprints, depending on the number of question types, integrations, and compliance requirements.

4

Integration and pilot wave

We test integrations with HRIS, CRM, EHR or data warehouse systems first in a staging environment using synthetic respondent data, then with a pilot wave of a few dozen real respondents, and only then across the full population. This includes training for researchers or HR staff who want to set up waves themselves.

5

Rollout and ongoing development

After go-live we provide support with monitoring, OS updates for iOS and Android, security patches, and further development. Many survey apps grow organically: a second language, a new questionnaire module, an expansion to another country or a new target group, and the maintenance contract keeps that running smoothly.

Frequently asked questions.

What clients usually want to know before starting a custom survey app.

When are SurveyMonkey or Typeform really not sufficient?
For a one-off survey with straightforward logic and non-sensitive data, those tools are usually perfectly adequate and cheaper. Custom software pays off when at least one of three things applies: you want data ownership (no respondent data on US servers), your routing or multi-wave logic doesn't fit the standard tools, or you want answers to land directly in your own systems without manual exports. In the first conversation we give you honest advice. Sometimes an off-the-shelf SaaS tool with a custom integration is the smarter route.
How exactly does offline mode work?
With a well-built offline-first app, respondents or interviewers notice no difference between working with or without a network connection. Answers, photos, audio recordings and signatures are stored locally in encrypted form and sync automatically as soon as a connection is restored. For longer fieldwork sessions, the entire questionnaire, including any images, is cached in advance. A key requirement is thoughtful conflict resolution (what happens if the same respondent starts on several devices?) and testing against realistic scenarios: aeroplane mode, poor 4G, a basement or a metal building. For related offline use cases, you may also want to look at our field service app page, which uses the same sync engine.
How does this work with GDPR, informed consent and data retention?
All communication is encrypted by default, both in transit and at rest, with an informed consent screen where respondents give explicit consent for each data category and can withdraw it afterwards. We apply data minimisation (only the fields strictly necessary for the research) and automatic retention policies per data category (for example, anonymising free-text answers after six months, while keeping scores for longer). For projects involving personal data of customers, employees or patients, we carry out a DPIA as standard and, in the final sprint, a penetration test by an independent security partner.
And what about research involving children or young people?
Research with minors is subject to additional GDPR rules on consent via a parent or guardian. Furthermore, the Code for Responsible Marketing of Food Products and the wider Children's Advertising Code impose strict rules on incentives and data use aimed at young people. We build the consent flow around this (digital signature from a parent or guardian), limit the number of fields we store, and take into account the age thresholds relevant to your research, for example 16 for GDPR consent and 13 for certain platform requirements.
Do you work with the EU AI Act for profiling?
If survey answers are used to automatically place a respondent in a segment, give advice, or calculate a score that affects a service or treatment, this quickly falls under the EU AI Act's provisions on profiling and automated decision-making. We help you assess whether this applies, document the logic transparently, and design the informed consent flow so that respondents know their answers are processed automatically. For sentiment analysis of open answers or intelligent routing, we sometimes draw on our AI development expertise.
What compliance applies to research in healthcare?
For healthcare research, in addition to GDPR, the NEN 7510 standard for information security applies. Depending on the nature of the research, the WGBO (Dutch Medical Treatment Contracts Act), the WMO (Dutch Medical Research Involving Human Subjects Act) and the code of conduct of your ethics committee may also apply. We work with healthcare organisations that administer patient-reported outcome measures (PROMs) and support the NEN 7510 requirements (logging, role-based access, encryption, physical and logical separation) as standard. We can connect to HiX or ChipSoft via HL7 or FHIR where your EHR allows it, and exports to REDCap for academic follow-up research are a frequently requested option.
Which integrations are available as standard?
In practice, almost anything. For HR: AFAS, Visma, Personio, BambooHR. For CRM: HubSpot, Salesforce, Microsoft Dynamics, Pipedrive. For marketing automation: Marketo, ActiveCampaign, Mailchimp. For healthcare: HiX, ChipSoft, REDCap. For BI and analytics: Snowflake, BigQuery, Azure Synapse, Power BI, Tableau, Looker. NPS scores are often also fed into a customer data platform so that all customer signals come together in one place. For lesser-known systems, we build the integration based on their API or, where none exists, through an intermediate layer.
Native app or a web survey on a mobile site?
For pulse measurements among employees and NPS mailings, a web survey on a mobile site is often sufficient: low-threshold, no installation required, and the respondent clicks through from an email or Teams message. For fieldwork, patient PROMs, panel research with multiple measurement moments, and anything with an offline requirement, we almost always opt for a proper native app, because you need camera access, GPS, reliable offline storage and push notifications. In the first conversation we advise which combination works best; often it's a mix: native for the demanding use cases, web survey for the lighter ones.
How long does a project take?
That depends heavily on the number of question types, the number of integrations, the compliance context and how many respondents need to be tested before going live. A first working version of a clearly defined pulse app with one integration can be ready within a few sprints. A larger implementation with multiple measurement waves, complex routing, EHR integration and phased pilots is a project spanning several sprints. We aim to get a first working version into the hands of real respondents as early as possible, because that is when you find out where the design needs adjusting.
What determines the cost?
Four factors define the scope: the number and complexity of the question types (a simple Likert scale is very different from a drag-and-drop ranking with geolocation), the number of integrations with existing systems, how much compliance layer is needed (standard GDPR versus NEN 7510 with a DPIA and penetration testing), and the rhythm of ongoing development afterwards (a one-off delivery or continuous maintenance with regular new waves). We work with fixed sprint budgets, so you know what you are spending each sprint and what it includes. In the first conversation we give an indicative estimate; after the discovery sprint, it becomes concrete.
Do you work alongside our own researchers or developers?
Yes, in many of our engagements that is the norm. Many clients have their own research team or methodologist who supply the questionnaire content, and possibly an IT team that manages the EHR, CRM or HRIS. We focus on the mobile layer and the integration APIs. We work in the same Git repository, use the same code conventions, and pair-program where it helps knowledge transfer. By the end of the engagement, your own developers can maintain the codebase fully independently, with no lock-in to us as a supplier.
Who manages the app after it goes live?
You can do that yourselves if you have in-house developers: we deliver the codebase, documentation and a runbook so your own team can maintain the app. Many clients opt for our management contract, covering monitoring, OS updates (iOS and Android versions periodically require adjustments), security patches and further development for a fixed monthly fee. Combinations are also possible, for example your team handling the questionnaire content and us handling the mobile layer.

Talk to us about your survey app.

A half-hour introductory call, with no obligation. We listen to your research question, ask about your respondents, target group and current tooling, and give you direction you can use, including if the advice is to try an existing SaaS tool first or to choose a hybrid approach. For related variants, you can also look at our pages on app development, customer data platforms, AI development and data engineering platforms.

Edit content