The maker has left
The app was built by a colleague who no longer works there. The team uses it every day, but nobody feels like the owner anymore.
Get help with this situationFIRST AID · CANVAS APPS
Your Canvas app is stuck.I'll take a look.
Many Canvas apps start on the shop floor: someone picks up the job and builds something that works. But after a few years the app has grown, its maker has left, or something is stuck that nobody dares to touch anymore. I help make such an app reliable again.
POWER FX · POLISHED DAILY
A formula can work — and still slow your app down.
A few examples of issues I run into and optimise in Canvas Apps.
Formulas.fxas left behind
fx
Filter(
Customers,
StartsWith(Name, txtSearch.Text)
)Non-delegatable Lower()Dataverse filters server-side — even at a hundred thousand records.
Five real-world patterns — from delegation to architecture. Your formulas get the same treatment.
POWER FX CHECK
Paste your formula. I'll look over it.
Paste your Power Fx formula and get a readable check straight away: delegation risks, N+1 patterns and other pitfalls that get expensive later.
Your formula is used only for this analysis and isn't kept, unless you choose to save it below.
UNDER THE HOOD
The problem often isn't in what you see.
But in what the app is doing in the meantime. On the left the formula, on the right what Power Apps Monitor sees — in this example a gallery of 50 rows.
POWER FXunoptimised
LookUp(
Accounts,
Account = ThisItem.Account.Account,
Name
)LIVE TRACE
Press play and follow along with the trace.
unoptimised
—
optimised
—
total duration
—
requests
—
transferred
—
Illustrative Monitor trace: one query for the gallery plus a separate lookup per row — 51 requests instead of one. No client data.
BEFORE AND AFTER
A screen can work — and still slow everyone down.
A Canvas app does not always need to be reinvented. A clear structure, logical navigation and obvious actions can already make a major difference.
BeforeA perfectly fine-looking screen
Canvas App
Edit request
In progressAfterSame screen, better thought through
CCanvas AppWorkspace
Back to overview
Request1
24
Details3Activity
SubjectWarehouse renovation
RequesterJ. de Vries
StatusIn progress
Date12 September 2026
At a glance
Key information together
Next action immediately visible
Less distraction on screen
1One task per screen, instead of five things at once
2What to do next sits at the top — not at the bottom
3Data that belongs together, sits together
4One clear next step, instead of four risky buttons
Representative visualisation of a possible Canvas app improvement. This is not a literal client interface and contains no client data.
WHERE YOU RECOGNISE YOURSELF
Four situations I often encounter.
Such an app is almost always built with good intentions, by someone who wanted to make a difference in their department. That deserves respect — and a solution, not a write-off.
Getting slower and slower
The app worked fine at first, but with every addition it got slower. Opening takes ages, saving takes ages, and people invent workarounds.
Get help with this situationIt stopped working
After a change, an update or a data migration something broke. And nobody knows exactly where it goes wrong.
Get help with this situationNobody understands it anymore
Too many screens, formulas on formulas, no documentation. Changing something feels like gambling: it might break something else.
Get help with this situationHOW IT WORKS
From recognition to solution.
We start without obligation. Whatever comes next, we agree on it upfront.
- 01
Introduction
You tell me what's going on and what the app does. I listen and ask targeted questions. This introduction is without obligation.
- 02
Agreeing the analysis
If it turns out to be worth examining the app properly, we agree upfront what that analysis involves and costs. So you know where you stand before I start.
- 03
Repair or rebuild
I repair what's broken, make the app faster and easier to understand, or explain what's structurally needed. Afterwards you know exactly what I did and why.
Does the problem turn out to be bigger than the app itself? I'll tell you honestly. In that case you can bring me in for a defined project or on an interim basis — but that's your call.
WHY ME
Canvas apps are my daily work.
- Hands-on: I build in Canvas Apps myself every day, from form to integration.
- Independent: I don't sell licences and have no stake in an expensive solution.
- Respect for the maker: such an app was built with care once. I don't tear it down, I make it workable.
GETTING STARTED
Let's see what's going wrong.
Tell me in a few lines what your app does and where it gets stuck. I reply personally, usually within one working day.