GSoC 2026 Introduction - Muhammad Waleed Aslam - WebSocket/gRPC DevTools

[Waleed Bhatti]

Hi Dart Team,

My name is Muhammad Waleed Aslam. I am a Software Engineering student in my 6th semester at the University of Sargodha, Pakistan (GPA 3.58), and currently working as a Flutter Developer Intern at Switch2iTech.

I am applying for the "Add WebSocket/gRPC Support to Flutter DevTools Network Panel" project for GSoC 2026.

I have studied issue #9507 carefully, including the HTTP profiling implementation history (the _HttpProfile scaffolding, VM service extensions, dart:developer APIs, and http_profile package work) that the WebSocket support would mirror. I also looked at Brian Quinlan's recent work on the web_socket and web_socket_channel packages.

I have two technical questions before I finalize my proposal:

1. web_socket_profile vs http_profile
In issue #9507, srawlins raises the open question of whether WebSocket profiling data should live in a new web_socket_profile package, or be added to the existing http_profile package. Has a decision been made here? The answer significantly affects how I scope the proposal — specifically steps 3 and 4 of the WebSocket plan.

2. Scope of the GSoC project
The full 5-step plan in #9507 (dart:io → VM service → http_profile → package integrations → DevTools UI) is substantial. For the Medium (175 hour) sizing, which steps are considered the core deliverable, and which would be stretch goals?

For background: I have built two production Flutter apps — a Crusher Management System and a Poultry Management System — both using Dio for HTTP, JWT auth, Provider state management, and Supabase. My portfolio is at https://waleedbhatti83.github.io

I am currently working on the ProfileableWebSocket sample project described in the idea list and will have it ready as a secret gist before the deadline.

Thank you for your time.

Best regards,
Muhammad Waleed Aslam
https://github.com/WaleedBhatti83

[Samuel Rawlins]

Hi Waleed, sorry for the delayed response!

On Sun, Mar 22, 2026 at 10:13 PM Waleed Bhatti <waleedb...@gmail.com> wrote:

Hi Dart Team,

My name is Muhammad Waleed Aslam. I am a Software Engineering student in my 6th semester at the University of Sargodha, Pakistan (GPA 3.58), and currently working as a Flutter Developer Intern at Switch2iTech.

I am applying for the "Add WebSocket/gRPC Support to Flutter DevTools Network Panel" project for GSoC 2026.

I have studied issue #9507 carefully, including the HTTP profiling implementation history (the _HttpProfile scaffolding, VM service extensions, dart:developer APIs, and http_profile package work) that the WebSocket support would mirror. I also looked at Brian Quinlan's recent work on the web_socket and web_socket_channel packages.

I have two technical questions before I finalize my proposal:

1. web_socket_profile vs http_profile
In issue #9507, srawlins raises the open question of whether WebSocket profiling data should live in a new web_socket_profile package, or be added to the existing http_profile package. Has a decision been made here? The answer significantly affects how I scope the proposal — specifically steps 3 and 4 of the WebSocket plan.

I strongly suspect we will want to shoe-horn any new WebSocket support and even gRPC support into the existing http_profile package. 

2. Scope of the GSoC project
The full 5-step plan in #9507 (dart:io → VM service → http_profile → package integrations → DevTools UI) is substantial. For the Medium (175 hour) sizing, which steps are considered the core deliverable, and which would be stretch goals?

Great question. It could be that covering all of the relevant packages in "package integrations" would be a stretch goal. I would definitely want to get at least _some_ WebSocket support all the way to the DevTools UI in this project. 

For background: I have built two production Flutter apps — a Crusher Management System and a Poultry Management System — both using Dio for HTTP, JWT auth, Provider state management, and Supabase. My portfolio is at https://waleedbhatti83.github.io

I am currently working on the ProfileableWebSocket sample project described in the idea list and will have it ready as a secret gist before the deadline.

Thank you for your time.

Best regards,
Muhammad Waleed Aslam
https://github.com/WaleedBhatti83

--
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/133c6ae7-372f-45bb-ad14-cc8a8c2b3ad4n%40googlegroups.com.

[Waleed Bhatti]

Hi,

Thank you for the clarification — this is very helpful.

I will update my proposal to reflect the following:

1. WebSocket profiling data will be added to the existing http_profile package rather than a new separate package.

2. The core deliverable will be end-to-end WebSocket support reaching the DevTools UI — covering dart:io, VM service, dart:developer, and the http_profile package. Full integration across all related packages (web_socket_channel, cupertino_http) will be treated as a stretch goal.

I have already submitted a draft proposal on summerofcode.withgoogle.com and will update it before the March 31 deadline to reflect both points.

My ProfileableWebSocket code sample is available here: https://gist.github.com/WaleedBhatti83/cadd2d1f2979a954bc7847f83083db0c

Thank you again for your time.

Best regards,
Muhammad Waleed Aslam
https://github.com/WaleedBhatti83