Blazor developers hand-build throttling for frequent UI events
Blazor developers handling events such as mouse movement and dragging lack an idiomatic way to debounce or throttle callbacks. Their workarounds rely on custom JavaScript interop, which people describe as clunky and repetitive; frequent callbacks can also overload the runtime and make the UI lag. The evidence primarily points to this event-handling problem, rather than the separate requests for DOM transitions or client-side analytics.
For blazor application developers. Mentioned from May 2019 to Mar 2024 on GitHub.
5 different people described this problem in 3 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 6.0/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Low
What people said
Quoted word for word. Follow a link to read the whole discussion.
Really don't want OnMouseOver event firing a million times sending Signal R messages at that rate. I know there is a way around this with custom JS but it's a huge hassle
In high-performance events like dragging I am noticing the ondrag event absolutely smash doruntimeinvoke during periods of significant mouse movement. This results in significant delays in the events being called and in turn, a lagging UI experience
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 4 more quotes from people who have this problem
- Current workarounds, existing solutions and risks