Re: [dart-gsoc-discuss] Subject: [GSoC 2026] WebSocket/GRPC DevTools: Handling High-Frequency Stream UX

22 views
Skip to first unread message

Samuel Rawlins

unread,
Mar 29, 2026, 11:47:01 AM (yesterday) Mar 29
to Vineet Hegde, dart-gsoc
Hi Vineet,

Thanks for the questions. DevTools is staffed with a small team, so we must consider possible new features and enhancements against the cost of maintenance, and especially against other features we could instead develop.

Features to support high-volume data could be very useful to some teams, but I think we'd need to push out the WebSocket support, and then wait for feedback. We can also pre-emptively see if Chrome DevTools has special support for high-volume data, but the priority of the feature would still need to take into account any requests from real-world users.

On Thu, Mar 26, 2026 at 10:59 AM Vineet Hegde <vineeth...@gmail.com> wrote:

Hi Elliott and Samuel,

While my proposal focuses on dart:io and VM Service instrumentation, I’ve been thinking ahead to the DevTools frontend UX for high-frequency WebSocket streams.

To handle large volumes of frames, would stream-management UI controls be worth considering? For example:

  • A “pause” toggle to freeze rendering while background traffic continues

  • Directional filtering (incoming vs outgoing)

This is not a change to my proposal scope, just a small UX consideration for a potential post-MVP enhancement.

I’d be interested in your thoughts on how developers should interact with this kind of high-volume data in DevTools.

Best regards,
Vineet Hegde

--
You received this message because you are subscribed to the Google Groups "dart-gsoc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dart-gsoc+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dart-gsoc/1b8af23e-0ca7-4d7b-908b-4e559f3dd36en%40googlegroups.com.

Vineet Hegde

unread,
4:08 AM (17 hours ago) 4:08 AM
to dart-gsoc
Hi Samuel,
Thanks for the clarification.
I agree on prioritizing initial WebSocket implementation and iterating based on real-world feedback. I’ll keep my focus on delivering stable instrumentation first and treat advanced UI controls as post-MVP enhancements.
Appreciate the guidance!
Best,
Vineet
Reply all
Reply to author
Forward
0 new messages