Service · App development

Custom survey app development.

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

Offline modeBranching logicGDPR-proofReal-time analytics

A survey app is more than a digital questionnaire.

The average survey tool — SurveyMonkey, Typeform, Microsoft Forms, Google Forms, Qualtrics or one of the dozens of variations on them — is perfectly fine for a one-off study with thirty respondents and a few simple questions. But as soon as the work grows, the target group changes, or the answers need to end up somewhere other than an Excel export, those tools hit their limits. A serious survey app does more: it goes out into the field with you, works without a network, adapts to what the respondent has already answered, and sends the data straight 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, there is also the organisation that could carry on perfectly well with Typeform or SurveyMonkey, but has one of three problems that an off-the-shelf package can't 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 need to go to a specific integration in a custom format, or they simply don't want their respondent data sitting on a server in the United States. For those scenarios, a custom solution pays off because the flexibility and data ownership you gain quickly earn back the extra investment.

A custom survey app adapts to you, not the other way round. Together with you, we map out which questions are asked, to which respondents, in what context, and what follow-up or aftercare is attached. Based on that, we design an app that gives respondents a pleasant experience — because a low drop-out rate is exactly what your research or pulse measurement stands or falls by — and that gives you, as the client, full control over the data, the planning and further development. If you'd like to get a broader picture of what a custom app involves first, see our page on app development for the general approach.

Three types of survey app we often build.

The approach differs depending on who needs to respond, in what context and what needs to happen with the data. In the first conversation, we'll advise which form best suits your research.

Compact project · fixed sprint budget

Pulse and NPS app for internal measurements

For HR and customer success: short questionnaires that are repeated regularly with the same group. Employee pulse surveys, customer NPS, student evaluations or supplier satisfaction. Push reminders at agreed intervals, anonymisation where needed, and a dashboard that shows trends per team or segment at a glance. Often integrated with an HRIS or CRM so that respondent segmentation is always accurate.

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 enforcement officers who conduct surveys on location. A fully offline app for tablet or phone: interviewers carry out questionnaires in shopping centres, at events, in deprived neighbourhoods or in a care facility without wifi, and the responses sync as soon as there is a connection again. Includes photo and video questions, geolocation capture and interviewer instructions in 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 long-running research with multiple measurement points per respondent, complex 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 almost every survey app, however different the content of the research. We build this layer from scratch each time, tailored to your questionnaire, target group and compliance context.

  • Branching logic and conditional skipsHide, show or rephrase questions based on earlier answers, demographics or a previous measurement wave. Far beyond the often restrictive if-then skip logic of off-the-shelf packages, including score-based routing and behavioural logic.
  • Offline mode that doesn't cause drop-outRespondents and interviewers can work entirely without a network. Answers, photos, video and signatures are stored locally in encrypted form and sync automatically as soon as there is a connection again. No lost responses.
  • Multi-language and regional variantsQuestionnaires in multiple languages, with correct translations for scale items (a 5-point Likert scale in Polish uses slightly different wording than in Dutch) and regional formats for dates, currencies and addresses.
  • Multi-modal question typesBesides text and multiple choice, also photo uploads, video questions, audio recordings, scale sliders, drag-and-drop ranking, map input for geolocation and hand-drawn input. For when a question genuinely calls for something other than a radio button.
  • Push reminders and reminder cadenceTargeted push notifications at agreed moments, with decreasing frequency for non-responders and personalised reminder texts based on your relationship with the respondent.
  • Real-time analytics and exportsA dashboard where researchers, HR managers or customer success teams can see live how a wave is progressing, 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 consent per data category, the ability to withdraw consent afterwards, retention policies per field, and pseudonymisation or anonymisation on export. GDPR-proof by design, not as a sticker added afterwards.
  • Native iOS and AndroidWe usually build in Flutter or React Native, so a single codebase runs on both platforms, with native performance for the camera, GPS, offline storage and push notifications. Pure native iOS or Android on their own is also possible if the requirements call for it, for example with integrations for 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 studies and 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 price. Includes monitoring, backups and a dedicated contact for researchers who want to set up new waves.

When custom is better than SurveyMonkey or Typeform.

Not every study needs its own app: for a one-off short questionnaire, the well-known SaaS tools are perfectly fine. Here are six signs that we see clients switch to a custom solution.

Data ownership

The data must not leave the building

For research in healthcare, government or HR contexts involving personal data, you don't want respondent data sitting on the servers of a US SaaS provider. Your own app on your own infrastructure or a European cloud solves that in one go, with clear data location agreements that you can stand behind when dealing with GDPR supervision.

Fieldwork

No network on location

Your interviewers conduct questionnaires in a care facility with poor wifi, out in the polder, at an event in a large hall, or at respondents' homes for a sample survey. SaaS tools work poorly or not at all offline, and you lose responses as soon as the connection drops. An offline-first app handles this completely.

Complexity

Routing too complex for the standard tools

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

Integration

The answers need to go somewhere specific

You no longer want to load Excel exports into a data warehouse or import them into a CRM by hand. The answers need to land directly in HubSpot, Salesforce, Marketo or your own data pipeline, with the right fields and transformations. SaaS integrations are often generic and require custom middleware, whereas a custom app has that layer built in.

Scale

The same study, over and over

You run a fixed measurement monthly, quarterly or for every new employee, customer or patient. With SaaS tools, you have to set up the questionnaire and export the data again every time. Your own app fully automates the cycle and builds up a longitudinal dataset that you can still analyse years later.

Branding

Respondents need to feel it's your study

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

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

How a survey app project works.

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 to the data at the other end. We immediately establish what an off-the-shelf package can do and where custom development pays off — honestly, even if the outcome is that Typeform is perfectly adequate for your case.

2

Questionnaire design and wireframes

Together with you, and a methodologist if needed, we design the respondent flow: what the opening text says, the logical order of questions, where the risk of drop-out lies, and how the informed-consent flow works. We test wireframes with two or three end users before we write a single line of code — because low drop-out starts with a good first impression.

3

Building in sprints

Every two weeks we deliver a working version of the app on your tablets and phones. You test along, a small pilot group of real respondents tests along, and we keep adjusting as we go. 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 first in a staging environment with synthetic respondent data, then with a pilot wave of a few dozen real respondents, and only then with the full population. This includes training for researchers or HR staff who want to be able to set up waves themselves.

5

Rollout and further 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 a maintenance contract keeps that running smoothly.

Frequently asked questions.

What clients usually want to know before we start on a custom survey app.

When are SurveyMonkey or Typeform really not enough?
For a one-off study with straightforward logic and non-sensitive data, those tools are usually fine and cheaper. Custom development 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 options, or you want answers to land directly in your own systems without manual exports. In the first conversation we give you honest advice — sometimes a SaaS tool with a custom integration is the smarter route.
How exactly does offline mode work?
With a well-built offline-first app, the respondent or interviewer notices no difference between working with or without a network. Answers, photos, audio recordings and signatures are stored locally in encrypted form and sync automatically as soon as a connection is available again. For longer fieldwork sessions, the entire questionnaire, including any images, is cached in advance. A key requirement is well-thought-out conflict resolution (what if the same respondent starts on several devices?) and testing in realistic scenarios: flight mode, poor 4G, in a basement or a metal building. For related offline use cases, take a look at our field service app page, where the same sync engine is used.
What about GDPR, informed consent and retention?
By default, all communication is encrypted in transit and at rest, with an informed-consent screen in which the respondent explicitly consents per data category and can withdraw consent 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 if it involves children or young people?
Research involving minors is subject to additional GDPR rules on consent from parents or guardians. Since the Code for Responsible Online Marketing of Food Products and the broader Code for Advertising to Children, there have also been strict rules on incentives and data use aimed at young people. We build the consent flow around these rules (a digital signature from a parent or carer), limit the number of fields we store, and take specific account of the age limits relevant to your research, for example 16 for GDPR consent and 13 for some platform requirements.
Do you work with the EU AI Act for profiling?
If the answers to a questionnaire 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 provisions on profiling and automated decision-making. We help you assess whether this applies, document the logic transparently, and build the informed-consent flow so that respondents know their answers are processed automatically. For sentiment analysis on open answers or intelligent routing, we sometimes bring in our AI development expertise.
What compliance applies to research in healthcare?
Research in healthcare is subject not only to the GDPR but also to the NEN 7510 information security standard. Depending on the nature of the research, the WGBO (Dutch Medical Treatment Contracts Act), the WMO (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 PROM questionnaires, and we support the NEN 7510 requirements (logging, role-based access, encryption, physical and logical separation) as standard. We build integrations with HiX or ChipSoft via HL7 or FHIR where your EHR allows it, and exports to Redcap for follow-up academic research are a frequently requested option.
Which integrations are possible 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 also often end up in a customer data platform so that all customer signals come together in one place. For lesser-known systems, we build the integration using their API or, if there isn't one, via an intermediate layer.
Native app or a web survey on a mobile site?
For pulse surveys among employees and NPS mailings, a web survey on a mobile site is often enough: low threshold, no installation, and the respondent clicks through from an email or Teams message. For fieldwork, patient PROMs, panel research with multiple measurement points and anything with an offline requirement, we almost always choose a true native app, because you need camera access, GPS, reliable offline storage and push notifications. In the first conversation, we advise which combination works best. It is often a mix: native for the heavy use cases, a web survey for the light 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 production. A first working version of a clearly scoped 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 of several sprints. We aim to get a first working version into the hands of real respondents as early as possible, because that is when it becomes clear where the design needs adjusting.
What determines the cost?
Four factors determine the scope: the number and complexity of the question types (a simple Likert scale is a different matter from a drag-and-drop ranking with geolocation), the number of integrations with existing systems, how much compliance is required (standard GDPR versus NEN 7510 with a DPIA and pen test), and the pace of ongoing development afterwards (delivered once, or continuous maintenance with regular new waves). We work with fixed sprint budgets so you know per sprint what you are spending and what is included. In the first conversation we give an indicative estimate; after the discovery sprint it becomes concrete.
Do you work with our own researchers or developers?
Yes, in a large share of our projects that is the norm. Many clients have their own research team or methodologist who supplies 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 do pair programming where it helps with knowledge transfer. At the end of the project, your own developers can maintain the codebase completely independently, with no lock-in to us as a supplier.
Who manages the app after go-live?
You can do that yourself 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 maintenance contract: monitoring, OS updates (iOS and Android versions require periodic adjustments), security patches and ongoing development for a fixed monthly fee. Combinations are also possible, for example your team for the questionnaire content and us for the mobile layer.

Talk to us about your survey app.

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

Edit content