Service · App development

Custom sustainable app development, in substance and in technology.

A "sustainable app" has a double meaning. It can be an app that enables sustainability — CO2 tracking, ESG reporting, energy monitoring, circular sharing platforms — or an app that is itself built sustainably, with code and hosting that don't waste energy. We build both, ideally at the same time.

CO2 & ESGCSRD / ESPRGreen codingEfficient hosting

Two meanings, one build project.

When clients call us about a "sustainable app", they usually mean one of two things. The first group has a product or business goal: they want to help customers reduce their footprint, they have to report demonstrably on impact under the CSRD, or they see a circular revenue model emerging with software as its backbone. The second group is driven internally: they don't want to build an application that will keep guzzling unnecessary energy on clumsy infrastructure, and they want to be able to show that their digital products, at the scale of thousands of users, won't become the bottleneck in their own sustainability reporting.

In practice, those two meanings usually coincide. An organisation that is serious about its sustainability story can't afford to launch an app that measures a user's CO2 footprint while itself running unnecessary calculations on a hyperscale GPU because a developer once set it up that way. We build app development projects in which the sustainability functionality and the engineering discipline move forward in parallel.

Our clients in this field are ESG-conscious SMEs and enterprises, sustainability start-ups, energy companies, circular-economy players, municipalities and NGOs. What they have in common: they don't want a marketing app with "100% green" in the hero and a footprint that nobody verifies in practice. They want an application whose claims, data model, calculation rules and hosting choice stand up to an external auditor, a Green Claims Directive investigation or a critical customer.

Three types of sustainable app we build.

Depending on who the user is — a consumer, an employee or a compliance team — the emphasis of the functional design shifts. In the first conversation, we'll advise which form fits your challenge.

Compact project · fixed sprint budget

Consumer app for CO2, energy or recycling behaviour

A mobile app that gives your end users insight into their footprint, lets them track their energy consumption, monitor their recycling behaviour or take part in a circular platform. Personal dashboard, push notifications at relevant milestones, and integrations with smart meters, public transport data or bank PSD2 feeds. Also read how we use AI development to generate personalised, useful recommendations instead of generic tips.

CO2 trackingSmart meterPSD2 dataGamification
Mid-sized project · fixed sprint budget

ESG reporting and data point app for businesses

An app for your sustainability coordinators, location managers and data suppliers to collect data points, validate them and deliver them to the reporting platform. Intended as a smart layer around your existing CSRD tooling, or as a core component of your own sustainability stack. It follows directly on from our page on building CSRD-ESG reporting software.

ESRS data pointsWorkflowAudit trailOffline input
Larger project · fixed sprint budget

Platform app for the circular or sharing economy

A marketplace, sharing platform or take-back app that makes the physical economy circular: refurbished electronics, swap platforms, return logistics, reusable packaging or a second-hand stream of your own products. Inventory, product identity via a digital product passport, quality reporting and payments all integrated. Ties in with our page on a digital product passport.

DPPMarketplaceReturn logisticsQR / NFC

Functionality: what a sustainable app does in practice.

Eight functional building blocks that we often build or integrate. Which ones you need depends on your target audience, your reporting obligations and how much of the physical world you want to map.

Footprint

CO2 footprint per user or product

For consumers, a mobile app that builds a credible CO2 estimate from public transport data, bank transactions, energy meter readings or explicit input, with a clear source for every line so users understand where the figure comes from and what is an assumption. For businesses, the same principle at product, contract or service level, fed by internal data and sector emission factor libraries.

Energy

Smart meter and building sensor integration

Real-time energy consumption via the P1 port, smart meter APIs or building management systems (BACnet, KNX, Modbus). Aggregation to day, week and month level, anomaly detection when an installation draws unusually much, and integrations with dynamic energy tariffs so users can see peak and off-peak hours. See also building energy software for the broader data approach.

Travel

Mobility and commuting tracking

An app that records commuting, business trips and business flights via GPS detection, NS-Business, mileage claims or HR mobility data. Output goes to the employee (personal insight) and to the employer (aggregated, GDPR-compliant), so that scope 3 category 7 (commuting) and category 6 (business travel) are covered without shadow spreadsheets.

Recycling

Collection and return tracking

An app that lets consumers or employees hand in, scan or register waste, packaging or products. QR or NFC tags on packaging, a map layer for drop-off points, reward systems where they make sense, and hand-offs to your processor with demonstrable flow registration for the Dutch Environmental Management Act and Extended Producer Responsibility.

Supply chain

Supply chain transparency and provenance

An app for customers or buyers that shows the origin, certifications and environmental impact of each product: organic, fair trade, FSC, recycled content, local production. The underlying data comes from your PIM, supplier self-declarations or a DPP platform. It helps you make claims that comply with the Green Claims Directive, so marketing claims never drift away from what is in the system.

Circular

Sharing, swapping or take-back platform

A marketplace for refurbished, second-hand, swapped or rented goods. Inventory management for individual units instead of SKUs, a quality score per unit, a returns flow with payments, and an integration with your brand platform so the circular flow is part of your customer experience rather than a separate subsite.

Reporting

ESG and KPI dashboards

An app or dashboard layer for sustainability teams and management that shows current scores on material KPIs, progress towards reduction targets and outstanding data points. Set up so the figures on the dashboard are exactly the same as those going into ESRS reporting or stakeholder updates, with no parallel version of the truth in PowerPoint.

Behaviour

Engagement, nudges and behavioural design

For consumer and employee apps: well-considered nudges, milestones, comparisons with cohort averages and small rewards that genuinely shift behaviour without straying into greenwashing territory. We work with behavioural science experts here and test every nudge on actual change, not on vanity clicks.

Engineering: how we build the app itself sustainably.

The code, the architecture and the hosting determine whether an app draws a few watts or a few dozen watts per user. The difference scales with your user numbers, and it is usually free to achieve when you build it in from the start rather than retrofitting it.

Architecture

Server-side compute only where strictly necessary

Many apps do work on a server that could just as well run on the device itself: data transformations, small calculations, simple filters. We design APIs so that the device does as much of its own work as possible, and only genuine aggregations or multi-user operations go through the backend. Fewer server calls means fewer running processes, less network traffic and less energy per session.

Caching

Smart caching across multiple layers

A CDN layer, browser and app caching, and beneath that server-side query caching for data that doesn't need to be recalculated on every request. In practice: a product catalogue that changes daily doesn't need to be pulled from the database on every page view. At scale, this saves an order of magnitude in compute, and therefore electricity, per user served.

Frontend

Lazy loading, image compression and dark mode

Resources are only loaded when they come into view. Images are served in AVIF or WebP, automatically scaled to the device. A considered dark mode implementation that genuinely lights fewer pixels on OLED screens. No JavaScript frameworks that pull in more megabytes than the app returns in functionality.

Mobile

Battery-aware and offline-first

Apps that use GPS, sensors or background sync do so with respect for the battery. We batch network requests, use push mechanisms instead of polling, and build core tasks to work offline, so a user on a train, on a platform or in a building without coverage isn't suddenly stuck online-only and losing data.

Hosting

Energy-conscious cloud choices

Hosting with providers that are transparent about their energy sources and that run in regions with a cleaner power grid (for example Azure, Google Cloud or AWS regions with demonstrably low grid carbon intensity). No unsubstantiated "100% green" claims; instead a reasoned choice of region, transparency about PUE and, where relevant, locations with waste heat recovery. This ties in with the broader idea from our page on AI development: only deploy heavy models where they genuinely add value.

Scaling

Scalable up, and scalable down

Many architectures are built to run big. We also design them to run small when possible: serverless functions that scale to zero under low load, batch processes that run overnight on cheaper (and often cleaner) capacity, and monitoring that lets us find and switch off unnecessary workloads.

What you get at the end.

A production-ready sustainable app, plus the documentation and engineering rationale your own sustainability, IT and marketing teams need to substantiate the claims.

  • The app itself, for the right platformsNative iOS, native Android, or a progressive web app depending on your target audience. A production environment plus a staging environment so tests never run on real user data.
  • Backend, data model and APIsA backend designed for low compute load per request, a data model in which sustainability data follows the same audit discipline as financial data, and public or partner APIs if you want to open up your data.
  • Engineering rationaleA short architecture note setting out the choices we made on compute, caching, hosting region and data volume, along with the trade-offs we considered along the way. Not a marketing story, but a document that an external auditor or an internal security colleague can read.
  • Source references for all sustainability claimsEvery CO2, energy or impact claim the app shows to users can be traced in the data model back to a source record: which emission factor, which assumption, which source, which version. Essential under the Green Claims Directive and in internal assurance discussions.
  • Complete codebase and documentationSource code, build instructions, data model and infrastructure overview. Your own IT team or a successor partner can take it over whenever you choose.
  • Privacy and GDPR packageA DPIA for the processing that touches personal data (smart meters, mobility, identifiable consumer behaviour), clear privacy statements in the app, and a data model that respects data minimisation instead of storing everything "just to be safe".
  • App Store publication and updatesPublication on the App Store and Google Play under your own developer account, with a review process that we handle for you and monitor for the first few release cycles. The versioning strategy and update cadence are agreed with you up front.
  • Ongoing maintenance (optional)Security patches, monitoring, keeping up with OS updates, and further development in response to new reporting requirements or changing emission factors. Fixed monthly price, with four response-time tiers depending on how operationally critical your app is.
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 →

When a custom sustainability app is the right choice.

Many sustainability applications can start perfectly well from off-the-shelf software (Plan A, Position Green, EcoVadis, Sustainalytics, Watershed or a calculation tool from your industry association). We only recommend custom development when you recognise one of these patterns.

Your own brand experience

The app is part of your customer experience

A footprint app for an energy company, a returns app for a branded retailer, a sharing platform for a carrier: users see the app as your product, not as a third-party tool. Custom, because the visual identity, tone, flow and integrations are interwoven with the rest of your stack.

Non-standard data

Your target group or data source is unique

An NGO that collects volunteer data in a way that fits no standard package, a municipality that combines neighbourhood-level energy data with waste streams, an agricultural cooperative that reads out soil sensors. No SaaS product is built for your combination of data.

CSRD context

Connecting to a larger reporting platform

You have or are building a serious CSRD platform and want a mobile input app for local data suppliers, or a dashboard app for your leadership team. The app has to follow exactly the same data discipline as your reporting layer, which almost always calls for a custom integration. See also our page on CSRD software.

Circular model

A new revenue model with the app as its engine

A take-back flow, sharing platform or refurbished marketplace whose entire commercial logic lives in the app. No SaaS building block fits a new revenue model; the app and the backend are the business.

How a sustainability app project works.

1

Introduction and intent check

A conversation in which we learn what you mean by "sustainable" (functionality, engineering or both), which compliance context applies (CSRD, ESPR/DPP, Green Claims Directive, GDPR), who the user is, and which claims your marketing team and your lawyers will want to substantiate later.

2

Discovery with domain and data owners

Workshops with your sustainability team, data owners, product management and, depending on the scope, your legal or compliance department. We map out the data model, identify source systems and establish which claims the app will actually make. At the end you get a validated scope, an initial screen flow, and a document listing the sustainability claims along with the sources that support them.

3

Building in sprints with demonstrable progress

A working build every two weeks that your team and a number of real end users can test. We integrate with source systems (smart meters, PSD2, ERP, supplier APIs) early on, so integration risks don't blow up at the end. A first publishable version typically emerges from the first series of sprints; further features and integrations follow after that.

4

Privacy, security and claims review

DPIA completion, pen testing and a claims review in which we check, for each sustainability claim in the app, that the source rule holds up and that the wording is Green Claims Directive-proof. The aim: no surprises when a journalist, a regulator or a critical customer asks 'how do you know?'.

5

Rollout, monitoring and further development

App store publication, a phased rollout to your target audience, and monitoring of both functional KPIs (usage, retention) and technical KPIs (energy consumption per session, API load, error rate). Ongoing development in response to new reporting requirements, revised emission factors and user feedback.

Frequently asked questions about sustainable apps.

What clients in this field usually want to know before we start.

What exactly do you mean by a 'sustainable app'?
Two things at once. First: an app whose functionality serves a sustainability goal, such as CO2 tracking, ESG reporting, energy monitoring or circular flows. Second: an app that is itself built sustainably, with code and hosting that don't waste energy. In our experience, clients who are serious about the one also want the other, so we treat them as a single build project with two complementary workstreams.
How do you prevent greenwashing in the app copy?
By tracing every quantitative claim in the app back to a source rule in the data model: which emission factor, which assumption, which version. No '100% green' or 'CO2-neutral' in the copy unless the calculation and scope behind it are visible. If in doubt, we always advise checking against the Green Claims Directive framework and help you choose wording that is factually defensible.
Do you work in a CSRD, ESPR/DPP or energy context?
Often. For a CSRD context, we usually integrate with a larger reporting platform; see CSRD ESG reporting software development. For the ESPR (Ecodesign for Sustainable Products Regulation) and the mandatory digital product passport, see our page on digital product passport software. For an energy context (smart meters, dynamic tariffs, energy management), see energy software development.
How do you measure the footprint of the app itself?
We measure and report on a few concrete dimensions: data transfer per session (bytes), compute time per request (server and device seconds), number of API calls per active user per day, and the carbon intensity of the hosting region we choose. There is no single magic number, but there is a set of indicators that can be monitored in production and that we can steer on during maintenance.
Which cloud providers do you use, and why?
Usually Google Cloud, Microsoft Azure or AWS, with the region chosen on the basis of grid carbon intensity and data centres covered by verifiable programmes (Climate Pledge, carbon-neutral claims, or EU emissions trading as concrete substantiation). We don't choose on marketing labels alone; we look at the actual energy mix per region and discuss that trade-off openly with you. For strictly EU-only or public-sector contexts, we also work with European hyperscalers and hosted Kubernetes providers within the Netherlands.
Which legislation does a sustainable app usually involve?
Almost always the GDPR (especially with smart meter, mobility and consumer behaviour data). For products and marketing claims: the Green Claims Directive and the upcoming ESPR with the digital product passport. For large companies that report: the CSRD with the ESRS standards. For energy applications: the relevant Dutch grid operator requirements and P1 port specifications. A good discovery phase establishes the applicable set for your specific case.
Do you work with our IT department and our sustainability consultant?
Almost always. Your IT team provides access to source systems and the cloud environment, your sustainability consultant contributes the methodological knowledge on ESRS, materiality or circularity, and our team builds the software and the integrations. In the final sprints we hand over knowledge so your own team can maintain it, or we continue the maintenance as an enterprise engagement with an SLA and monitoring.
Can a sustainable app also be attractive and enjoyable to use?
Yes, and it usually has to be if people are going to use it. A footprint app that feels strict and preachy in every session loses its users within days. We work with product designers who shape a tone and flow that are inviting and concrete, with clear visualisations of progress, small rewards at milestones and respectful messaging when things go less well. Here, sustainability is a subject, not a punishment mechanism.
What determines the cost of a custom sustainable app?
The biggest cost drivers are the number of platforms (iOS only, Android only, both, or a progressive web app), the number of external data sources we integrate (smart meter, PSD2, ERP, supplier APIs), the complexity of the sustainability calculations, and whether you connect to an existing backend or build from scratch. We only give an honest estimate after the scoping session. We have a page on custom software costs that explains the logic.
How long until we can go live?
A first publishable version of a well-defined app, for example a footprint app for a single source system, is usually ready within a few sprints. A full platform with multiple sources, its own marketplace or a deeply integrated ESG reporting app is a multi-sprint project, with a pilot launch as the first delivery followed by phased expansion. We work with fixed sprint budgets so you can adjust the pace and scope along the way.

Talk to us about your sustainable app.

A no-obligation introductory call of half an hour. We listen to your challenge, whether it is functionality, engineering or both, and give you direction you can actually use, even if a standard platform turns out to be the better choice. See also app development for our broader approach.

Share LinkedIn Email

Edit content