The Problem with Claiming UI/UX Design for SR&ED

In the modern software landscape, a compelling User Interface (UI) and intuitive User Experience (UX) are often the difference between a product's success and failure. However, when it comes to the SR&ED program, the CRA draws a very rigid line separating design from experimental development.

The General Rule: UI/UX is Ineligible

The CRA's primary stance is that UI/UX design falls under the category of "routine engineering" or "artistic design," both of which are explicitly excluded from the SR&ED program.

Why? Because the challenges designers face—while complex from a human psychology or business perspective—are rarely technological uncertainties.

Determining the optimal placement of a checkout button, designing a seamless onboarding flow, or creating a visually appealing dashboard using standard CSS and JavaScript frameworks relies on established knowledge and continuous user testing. There is no underlying technological impossibility preventing the building of those screens.

When Design Bleeds into SR&ED

While the act of designing the interface is ineligible, the structural engineering required to support a novel interface sometimes qualifies. You must draw a clear distinction between the "look and feel" and the "underlying mechanics."

The "Novel Mechanics" Exception

If a design requirement forces the engineering team to solve a technological uncertainty, the engineering effort (not the design effort) may be eligible.

Example 1: Real-time Data Rendering A UX designer requires a dashboard to render 10 million data points instantly without freezing the browser thread. If standard charting libraries (like Chart.js or D3) crash under this load, the engineering team may need to build a custom WebGL rendering engine and implement complex data-decimation algorithms. The effort to build that rendering engine is SR&ED; the UX research dictating how the chart should look to the user is not.

Example 2: Unprecedented Device Integration If an interface requires capturing and processing novel biometric data from a new wearable device in real-time, the low-level integration algorithms are likely eligible. The UI presenting that data is not.

Protecting Your Claim

If you include frontend developers in your SR&ED claim, be exceptionally careful with your technical narratives. Never describe their work as "improving the user interface" or "enhancing user interaction."

Instead, focus entirely on the backend and architectural hurdles—such as state management complexities, memory leaks in the browser, or novel data synchronization techniques—that were required to support the application's demands.