Build help into Power Apps yourself or buy an in-app guidance tool: how do app owners decide?
The Direct Answer
For organizations with several apps or frequent change, buying an in-app guidance tool is the better route: model-driven help panes are set per app and per form, lack sequential balloons, and need maker time for every change, multiplied across apps. Building it yourself fits a narrow case: one stable model-driven app with a small user base.
Deeper Explanation
The decision turns on maintenance more than on what you can build, and maintenance is where building gets expensive. In model-driven apps, including Dynamics 365, makers can create custom help panes with coach marks, help balloons and linked videos, but each pane is set per table, form, dashboard, language or app, so help is built and kept current one form at a time. Microsoft also documents the limits: the panes do not work on mobile devices, sequential balloons are not supported yet, and balloons do not work well with custom components. In canvas apps, help is built from the app’s own screens and controls. Microsoft calls the component library the recommended way to reuse components across apps, yet every update must be published and then accepted by the maker of each app that uses it. Each screen change therefore costs maker time, repeated for every app. A digital adoption platform (DAP) is software that places guidance, such as step-by-step walkthroughs and short help, inside the applications people already use, and it moves that upkeep out of the apps. With VisualSP’s digital adoption platform, for example, one team writes and updates guidance centrally and it appears across Power Apps, Dynamics 365 and Microsoft 365 without changing any app’s code. Timing matters on either route: Nielsen Norman Group finds that upfront tutorials interrupt users and are quickly forgotten, so whichever route you take, put help at the step where people need it. Help in context is what turns a launched app into feature adoption and realized value.
The Research
- Custom help panes in model-driven apps support rich text, coach marks, help balloons and linked videos, and are stored as Dataverse solution components, per Microsoft Learn’s guide to custom help panes; they do not work on mobile devices.
- Component libraries are Microsoft’s recommended way to reuse canvas app components across apps, but each consuming app’s maker must review and accept a published update, which is the hidden maintenance cost of home-built help.
- Upfront tutorials interrupt users, do not necessarily improve task performance and are quickly forgotten, while contextual help is triggered when users need it, according to Nielsen Norman Group.
Strategy and Actionable Steps
- Count the apps and processes that need help. Each additional app, and each canvas app that needs its own help screens, adds to both the build and the upkeep.
- Name who maintains help after go-live. Building ties every help change to a maker and a release. If the people who know the process are not makers, either budget for that dependency or choose a tool where they edit guidance centrally without touching the app.
- Check whether the process leaves Power Apps. Help built inside an app stays in that app. If the process continues in SharePoint, Teams or Dynamics 365, compare tools that cover each of those apps.
- Test both routes against how your users work. Native help panes have documented limits on mobile and on sequential balloons. Bought tools have mobile limits too: VisualSP offers only limited support on mobile devices with a large enough screen, and usually not walkthroughs. If most users work on phones, neither route gives full step-by-step guidance there.
- Compare both routes on one process, at full cost. Put native help and a tool’s guidance on the same screen, then compare the effort to publish, the effort to update after the next change, and whether errors or questions fall. Price both honestly: building reuses skills, licenses and solution processes you already have, while buying adds a subscription and a security and procurement review. Decide up front how you will know help is opened; VisualSP’s usage reporting, for instance, shows which walkthroughs each user opens and which apps draw the most use.
Building’s costs arrive after launch, in maker time for every change and help maintained app by app, which is why it suits only one stable model-driven app with a small user base and why buying is the better route once apps or changes multiply.
FAQ
Does Power Apps have built-in in-app help?
Model-driven apps do. Makers can add custom help panes per table, form, dashboard, language or app, with coach marks and balloons. In canvas apps, makers build help from screens and controls, often shared through a component library.
How much work is it to maintain help you build yourself?
It grows with the number of apps. With a component library, an update must be published and then reviewed and accepted in each app that uses it, and a component customized locally stops receiving updates.
When does buying an in-app guidance tool make more sense?
When help must cover many apps, change often, or be edited by process owners rather than makers. Business application owners responsible for several apps usually reach that point first: each new app adds another set of help to keep current, while a tool with central authoring lets one team update guidance for all of them in one place.
Can an in-app guidance tool work on top of Power Apps?
Many can, but check which kinds of app each one supports. VisualSP’s digital adoption platform works in both canvas and model-driven Power Apps, alongside Power Automate and Power BI, with interactive walkthroughs that guide users step by step through important processes. On desktop that covers the gap native help panes leave in canvas apps; on mobile, support is limited and usually excludes walkthroughs.
Should help be a tutorial at first launch or contextual tips?
Contextual tips, in most cases. Nielsen Norman Group found that tutorials interrupt users and are quickly forgotten, while help that appears at the moment of need is used when it matters, whether you build it or buy it.