Skip to content
TAA

App development in Breda

App development for Breda companies that work with the municipality

Apps for Breda firms whose client is a public body: documentation written with the Open Government Act in mind, accessibility to WCAG 2.1 AA. One architect, fixed price per step.

By , software architect · Last updated

When a Breda company builds an app for a municipality, what it hands over becomes information held by the municipality, which anyone can request under the Wet open overheid (Woo), subject to the grounds for refusal the Act sets. Breda had 190,204 residents on 1 January 2026 according to CBS, which makes it the ninth-largest municipality in the Netherlands, and like every Dutch municipality it falls under the Woo.

Documentation that can be read by the public

Public-sector documentation is written on the assumption that it may become public. Architecture descriptions, test reports and data-flow diagrams for the client contain what the client needs to run and audit the app. Internal working material, pricing logic and anything commercially sensitive stay in separate documents, clearly marked, so the municipality can weigh a request without having to untangle them first.

Deadlines and grounds for refusal

The ordinary decision period for a Woo request is four weeks, extendable by up to two weeks for volume or complexity. Statutory suspension grounds can affect that period. The Act lets the government withhold information on set grounds, among them privacy and the protection of competitively sensitive business data. Those grounds are weighed by the municipality case by case, not granted in advance, which is why clear marking and separate documents help a supplier more than a confidentiality stamp on everything.

Accessibility and data protection

A municipal app is assessed against EN 301 549, including WCAG 2.1 A and AA, subject to the statutory exceptions. If it processes personal data, the Autoriteit Persoonsgegevens is the supervisory authority; controller and processor roles depend on who determines the purposes and means of each processing activity. A supplier is a processor where it processes personal data on behalf of that controller. The app is built for both: accessible screens, and a data model with retention and access documented for the municipality's review.

  • Architecture Review at $10,500 to $13,900 for an app that has to pass a municipal tender or audit
  • First Version (MVP) from $27,800

The country-wide picture, including the BSN rule: Netherlands overview. For the security baseline government clients use, see The Hague. To discuss a project, get in touch.

Price, contract and data

  • Every step has a fixed price, set in writing before work starts; extra scope is added only through a change order you approve in writing.
  • The code sits in your repository from day one; with each paid milestone, the rights to everything delivered up to that point pass to you. Third-party components and pre-existing tools keep their own licences.
  • For rescues and new builds, 90 days of free bug-fixing after launch, on top of the 12-month warranty under the Terms. Ongoing operation starts at $1,400 a month.
  • You contract with DigitalFreedom Global LLC, Wyoming, USA. All prices are net; the tax treatment is clarified before contract and stated in the offer.
  • My infrastructure is in the United Kingdom and Europe. Where I process personal data on your behalf, we sign a data processing agreement (Art. 28 GDPR). The provider overview on digitalfreedom.co.za lists the subprocessors, their locations and the contractual safeguards.

Common questions

Can documents about our app be requested from the municipality?

Information that a municipality holds can be requested under the Wet open overheid (Woo), which applies to ministries, municipalities, provinces, water boards and other government organisations. The ordinary decision period is four weeks, extendable by up to two weeks for large or complex requests; statutory suspension grounds can affect it. It can withhold information on grounds set in the Act, among them the protection of competitively sensitive business data and of privacy.

How do we protect our business information in such a case?

By marking it clearly when you hand it over and stating why it is commercially sensitive. Whether a ground for refusal applies is decided by the government body; the marking helps it see what is at stake. The documentation for your client is written so that the parts meant for it and the parts that are internal to your company are kept apart.

Does the municipality's app have to be accessible?

Municipalities are covered by the Besluit digitale toegankelijkheid overheid. The applicable standard is EN 301 549, including WCAG 2.1 A and AA; the rules include content exceptions and provisions on disproportionate burden.

Talk to the architect who'll be accountable for your app

In a free, non-binding 30-minute call with me, we look at what happened, who holds which account and what it takes to get your app running smoothly with you covered; an NDA is available beforehand on request. You leave with a clear next step.

Free 30-minute call, no obligation

You talk to Marcel directly, the architect who is accountable for the work. No sales rep, no pitch.

The calendar is served by Cal.com. It loads only after you click (data goes to Cal.com, US). Privacy policy

Prefer to write first? Describe your situation, with a link to your app, repository or questionnaire. You get an answer within one business day.