Insights

The future of digital

Discover the trends, tech, and strategic insights shaping tomorrow's digital landscape. Written by experts, curated for innovators.

A new chapter for icapps with Sander Hofman as Managing Partner

icapps
October 29, 2026
·
5
min

Building on what’s there

During his eight years at icapps, Kris has helped shape the company with a strong commercial outlook, close client relationships, and a people-first approach to leadership. “In a changing market, I wanted to give our teams the space and trust to help shape how we move forward,” says Kris.

The handover to Sander builds on that work and brings a stronger technical focus to icapps’ next phase. 

Technology at the heart of our next chapter

Technology has always been at the core of icapps. With Sander in the lead, that expertise will play an even bigger role in shaping our strategy, guiding our investments, and helping clients move forward.

During his time as Head of Technology, Sander already helped strengthen collaboration across our teams and translate technical expertise into practical business value.

“Our clients need software they can rely on today and build on tomorrow,” says Sander. “That starts with understanding their ambitions and making technology choices that support them over time.”

Together with the management team, he will continue to deepen our expertise and put that approach into practice.


Looking beyond the hype

For clients, this means a partner equipped to work through increasingly complex technology choices. Where can a new capability make a meaningful difference? What needs to change before a business can scale? And when is strengthening an existing application the smartest investment?

Application modernisation remains an important part of that focus. Making essential software more secure, adaptable, and easier to maintain creates room for growth and a stronger basis for future innovation.

It’s the same curiosity and willingness to play devil’s advocate that guide our work: understand the challenge, question assumptions, and build something that keeps delivering value.

Giving innovation room to grow

That same thinking comes to life in SumZero, our AI spin-off, also led by Sander. Building on icapps’ technical expertise, it gives AI innovation the dedicated space and focus it needs to grow.

“With SumZero, we’re giving AI innovation the dedicated attention it deserves,” says Sander. “We’re building the expertise to turn its possibilities into solutions for real business needs.”

We’re grateful to Kris for the leadership and commitment that brought us here. With Sander taking the lead, we’re building on that foundation and putting our technological strengths firmly at the heart of what comes next.

‍

All insights

Digital strategy
Development
Innovation
Design
Culture
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Key insights from KotlinConf '26

icapps
June 7, 2026
·
3
min

The numbers & corporate adoption

  • Market Dominance: Kotlin is used in 92% of Play Store apps, and 86% of Android devs call it their primary language.
  • KMP Growth: The number of KMP apps in stores doubled over the past year, supported by 3,600+ ready-to-use libraries on klibs.io.
  • Enterprise Trust: Google Docs has been completely rewritten in KMP as part of a full Google Workspace migration, and Google Search is largely converted to Kotlin. Sony also demonstrated successful, phased KMP adoption in complex setups.

Tooling & performance gains

Kotlin 2.4 has officially gone stable, bringing core features like context parameters and explicit backing fields into production setups. The tooling updates focus heavily on optimizing performance and widening the ecosystem:

  • iOS & Build performance: Moving from Kotlin 2.2 to 2.4 yields a 25% reduction in build times and a 58% decrease in build RAM usage. Swift Export (now supporting suspend functions and Flows) and Swift Package Manager (SPM) integration have both successfully reached Alpha. Additionally, Liquid Glass UI-interop allows native components to blend seamlessly with Compose UI.
  • New Ecosystem tooling: A new uniform Kotlin CLI, a streamlined project structure for production applications, and an Alpha VS Code extension are expanding Kotlin's footprint far outside traditional IDE boundaries.

Android is officially "Compose-first"

Google has officially declared Android Compose-first, shifting traditional Views to maintenance mode. Writing a native app in Compose today ensures a much easier port to Compose Multiplatform (CMP) later since the UI layer is already portable. On the multiplatform side, Navigation 3 is now stable, CMP for Web is in Beta (with accessibility and HTML interop), and Hot Reload for Desktop is stable by default.

How the Ecosystem validates the icapps workflow

The announcements from KotlinConf '26 didn't catch us off guard; rather, they heavily validate our long-term roadmap and internal standards.

We were already compose-first

While the broader industry is currently adjusting to Google's massive push toward Jetpack Compose and KMP, Compose-first has been our internal standard for years. A prime example is our work for Bolero.

By minimizing our legacy XML footprint early on, our architecture is already optimized for modern development. For our partners, this mature foundation means any future transition to KMP or CMP will be significantly faster, cleaner, and more cost-effective. To capitalize on this, we are executing immediate action items to phase out our remaining legacy XML Views and test how Android’s new CLI can augment our automated testing.

Navigating the AI Shift: SDD and EDD

With JetBrains shaping future AI tooling via the open Agent Client Protocol (ACP), software engineering is actively shifting away from manual coding toward two new structural paradigms:

  • Spec-Driven Development (SDD): Writing highly precise technical specifications beforehand to act as a contract and regression check for AI agents.
  • Eval-Driven Development (EDD): Setting up rigorous evaluation guardrails (such as "AI as a judge") to actively combat hallucinations and context drift.

Moving forward, we will actively investigate how to integrate these key insights and guardrails into our own AI SDLC workflow to broaden its power even further.

While we are experimenting with the new Android CLI and Journeys to see how automated agents can safely speed up routine testing, we are balancing this with a healthy note of caution. Conference leaders highlighted critical industry nuances, including ethical concerns, potential senior burnout from a shrinking junior pipeline, and impending pricing "rugpulls" as VC-subsidized AI tools inevitably shift to heavy usage-based billing. Our focus remains on using AI to augment, not replace, our strict quality standards.

The bottom line: What it means for you

  • For Mobile Developers: The shift is absolute. Android is officially Compose-first, and KMP is rapidly narrowing the iOS gap with 25% faster builds and smoother Swift integration.
  • For Tech Leads & CTOs: KMP is enterprise-proven. With Google migrating Workspace and Search to Kotlin, KMP has graduated from an experimental framework to a risk-reduced strategy for scalable architecture.
  • For icapps clients: While we work purely native today, we are closely monitoring these advancements. We stand ready to adopt KMP and Compose Multiplatform (CMP) the moment the timing is right for your business.

‍

Development

When Bluetooth devices compete: how we solve multi-device BLE challenges

icapps
May 19, 2026
·
5
min

The challenge most apps underestimate

Once the platform scaled, new needs emerged:

  • Reliable location detection: To ensure users could always end their rides, even in GPS-poor environments like underground stations, we implemented Beacon technology as a vital fallback.
  • Maintenance access: Service teams needed dedicated BLE access to battery locks for maintenance purposes.

Suddenly, the app wasn’t talking to one device anymore. It was juggling multiple Bluetooth interactions at the same time.

And that’s where things started to break.

‍

One BLE radio, multiple demands

‍

Smartphones only have one Bluetooth radio. Yet many apps treat it like an unlimited resource.

In practice, this leads to:

  • Silent scan interruptions (especially on Android)
  • Features interfering with each other
  • Device-specific bugs that are hard to reproduce
  • “Works most of the time” experiences that frustrate users

For platforms like Blue-bike, this directly impacts both user experience and operations. To solve this, we leveraged our partnership to build a robust architecture that treats Bluetooth as a shared system resource.

‍

Our approach: treat BLE as a shared resource

‍

At icapps, we’ve seen this pattern before across multiple projects. When apps evolve, Bluetooth complexity grows with them.

Instead of patching issues later, we design for it upfront.

The key insight is simple: Bluetooth should be managed like any shared system resource.

Meaning: just as a processor decides which app gets processing power, there needs to be a system that determines which function is allowed to use the Bluetooth antenna at any given moment. Without this central management, different parts of the app (such as unlocking the lock versus searching for beacons) will compete with each other for the connection, leading to failed actions and a frustrated user.

The solution: a scan coordinator

To prevent conflicts between BLE features, we implemented a centralized scan coordinator.

In short, it:

  • Controls who can scan at any given time
  • Assigns priorities (user actions over background processes)
  • Temporarily pauses lower-priority scans
  • Applies rate limiting to avoid OS restrictions
  • Ensures consistent behavior across devices

This creates a predictable and stable Bluetooth layer, even as new features are added.

‍

Why this matters for your product

‍

If your app connects to just one device, you might never notice this problem.

But if you’re building:

  • A connected product ecosystem
  • A mobility or IoT platform
  • A feature roadmap with future integrations

…this challenge will surface sooner or later.

And when it does, it won’t show up in testing. It will show up in production.

‍

Designing for scale from day one

‍

What we built for Blue-bike is not a workaround. It’s a scalable foundation.

By centralizing BLE coordination:

  • User interactions become reliable
  • Background processes stay invisible but effective
  • New integrations don’t introduce new risks

Most importantly, it allows teams to keep innovating without breaking existing functionality.

‍

What this says about how we work

‍

This project reflects how we approach digital products at icapps.

We don’t just build what’s needed today.
We anticipate what your product will need tomorrow.

Because in connected ecosystems, small technical decisions can have a big impact on user experience.

If you’re working on a product with Bluetooth, IoT or multiple device integrations, it’s worth asking: Are we building for today’s use case… or tomorrow’s complexity?

‍

FAQ: Bluetooth and multi-device BLE

‍

What is multi-device BLE?

It refers to apps interacting with multiple Bluetooth Low Energy devices, common in IoT, mobility, and connected products.

Why does Bluetooth fail with multiple devices?

Because smartphones only have one BLE radio. Multiple scans or connections can interfere, causing unreliable behavior.

How do you manage multiple BLE interactions?

By using a centralized approach, like a scan coordinator, to control access, prioritize actions, and prevent conflicts.

What are common BLE issues in mobile apps?

Unstable connections, background limitations, Android restrictions, and conflicts between multiple Bluetooth processes.

When do you need a scan coordinator?

As soon as your app connects to multiple devices or combines background and foreground BLE features

‍

‍

European cloud alternatives: A shortlist of AWS replacements

icapps
January 26, 2026
·
3
min

Rather than listing every available option, we focused on providers that could realistically replace large parts of an existing AWS setup without disrupting modern development workflows. We are fully aware that there is no true drop in replacement for AWS and that a small number of services remain provider specific.

Instead, we deliberately focused on the areas where a well considered tradeoff is possible, aiming for a setup where at least 80% of applications can be deployed on either platform while prioritizing the most achievable wins.

How we defined “viable” European cloud alternatives

‍

We didn’t start with vendors. We started with requirements.

Our selection was based on European initiatives that map cloud providers operating fully under EU jurisdiction. From there, we applied a set of practical criteria rooted in day-to-day product development.

Our non-negotiables:

  • Kubernetes as a first-class citizen
  • Managed database services
  • Object storage as an alternative to S3
  • Compatibility with CI/CD pipelines
  • Scalability for internal and customer-facing applications

The goal was not ideological purity, but feasibility.

The shortlist

‍

Based on this approach, three European cloud providers stood out.

Hetzner

Hetzner is widely respected for its cost efficiency and reliable infrastructure. However, it lacks the managed services needed for teams that rely heavily on Kubernetes and managed databases. That would introduce additional operational complexity, which made it less suitable for our use case.

OVHCloud

OVHCloud offers an extensive and powerful portfolio. While that breadth is impressive, it also comes with complexity. Evaluating and adopting the right subset of services would require more effort than we were aiming for at this stage.

Scaleway

Scaleway struck the right balance.

Its services closely mirror common AWS workflows, particularly around Kubernetes, managed databases, and object storage. From a team perspective, this made the transition feel realistic rather than disruptive.

‍

Why familiarity matters when leaving AWS

‍

One of the biggest misconceptions about switching cloud providers is that everything has to change.

In reality, the closer a platform aligns with existing patterns, the lower the cognitive and operational cost for teams. Scaleway’s approach allowed us to keep our development philosophy intact while moving infrastructure under European jurisdiction.

‍

What this shortlist tells us

‍

There is no single “best” European cloud provider. But our first choice is Scaleway.

What this shortlist proves is that European cloud alternatives have matured. For organizations running modern, container-based workloads, moving away from US cloud providers is no longer a theoretical exercise.

‍

Is your business truly protected under EU jurisdiction? 

‍

As Belgian companies navigate evolving privacy laws and the complexities of international data access, European alternatives have matured into powerful, high-performance solutions. Use this checklist to evaluate your current "Cloud Sovereignty" score and discover if a move to a local provider is your next best move.

Take the 2-minute test!

‍

What’s next in this series

‍

In the next blog, we’ll move from selection to execution. We’ll share how we’re migrating applications to Scaleway and what that looks like in practice.

Development

Artificial intelligence in construction: how we built intelligent roof analysis for SCOPR.AI

icapps
December 15, 2025
·
7
min

‍

Understanding the goal of SCOPR.AI

‍

SCOPR.AI is designed to automatically assess roofs by focusing on their structural quality and layout. The system looks at key architectural features like how straight the eaves, ridges, and tiles are. By using advanced computer vision, the platform aims to make roof inspections faster, safer, and far more efficient.

However, building an AI model that delivers fast and accurate predictions in real time comes with significant technical hurdles. Our development team ran into several complex challenges along the way, from optimizing the model for mobile hardware to ensuring cross-platform stability. Here is how we tackled these problems.

‍

1. Making the artificial intelligence model fast and accurate

‍

For SCOPR.AI to provide real value to construction professionals, it needed to be both precise and exceptionally quick. Achieving high precision often requires heavy computational power, which naturally slows down processing times.

To solve this, we used special compression techniques to streamline the AI model and clean up the data it processes. This allowed us to maintain high accuracy while significantly increasing speed and processing efficiency.

‍

2. Getting artificial intelligence to run on mobile devices

‍

Mobile devices have limited processing power and battery capacity compared to cloud servers, which makes running complex computer vision models tricky. If an AI model is too heavy, it slows down user devices and drains the battery rapidly.

Our team resolved this by converting the original AI model into a lightweight version using TensorFlow Lite. We applied advanced size-reduction techniques without sacrificing the integrity of the results, allowing the software to work smoothly in real time on standard smartphones.

‍

3. Improving computer vision accuracy

‍

AI models can occasionally make mistakes or misinterpret visual data, especially when analyzing complex outdoor structures from different angles. We wanted to ensure that SCOPR.AI provided the most reliable assessments possible.

To maximize performance, we experimented with different AI structures, integrated pre-trained models to boost baseline recognition, and fine-tuned the way the system processes raw images.

‍

4. Making artificial intelligence predictions understandable

‍

Raw data generated by an AI model is rarely helpful to an end user. While the system can detect lines and angles, that data must be structured into clear, meaningful insights for a contractor or inspector.

We applied mathematical analysis to the raw output of the AI. This translation layer turns complex data points into intuitive, actionable information that anyone can read on site.

‍

5. Connecting artificial intelligence to different platforms

‍

SCOPR.AI needed to deliver a consistent experience across different platforms, from native mobile apps to web applications, without any technical hiccups.

To build a unified ecosystem, we linked our core AI systems, which were built using Python and TensorFlow, with Flutter for the mobile interface and Django for backend operations. This architecture ensures smooth, reliable communication between systems.

‍

6. Creating a scalable system architecture

‍

An intelligent application requires a solid backend system capable of handling multiple requests simultaneously and delivering predictions instantly.

We built a robust API using Django to act as a digital bridge between our systems. This allows the AI model to communicate seamlessly with different applications, ensuring the platform can scale as the user base grows.

‍

7. Keeping the artificial intelligence model up to date

‍

Machine learning models can become less accurate over time if they are not continuously updated with fresh data. This phenomenon, known as model drift, can compromise the reliability of structural checks.

We solved this by creating an automated retraining pipeline. This setup allows the system to learn from new data inputs continuously, meaning the artificial intelligence improves and adapts over time.

‍

Building smarter digital products

‍

Building SCOPR.AI was a journey full of technical challenges, but each obstacle provided an opportunity to innovate. From making computer vision mobile-friendly to ensuring long-term model accuracy, our team learned how to perfectly balance speed, efficiency, and scalability.

If you are currently planning an AI project or looking to modernize your current systems, these engineering lessons can help you build smarter, faster, and more adaptable digital solutions.

Innovation
Ready to bring

Clarity to your digital challenge?

Whether you’re modernising a complex IT landscape or building a digital product that must scale and last, it always starts with the right conversation.