
Dart is a client language for apps on any platform
Showing 5 of 27 projects. Click any project card for scope, mentors, and proposal studio.
Mentors: Student: Nourhan H.
When debugging Dart applications that use dart:ffi (Foreign Function Interface), developers encounter a frustrating limitation: Pointer objects appear as opaque memory addresses. For a Pointer<MyStruct> containing fields a = 42 and b = 3.14, the debugger shows only 0x7f8a4b3c2d10, not the actual data. This forces developers to rely on print statements or risky manual memory inspection, creating a significant blind spot when working with native code. This project aims to make native memory inspection a first-class debugging feature in Dart DevTools. By extending the VM Service Protocol, implementing safe pointer dereferencing, and enhancing DevTools' UI, developers will be able to inspect struct fields directly in the debugger without crashing on invalid pointers. The goal is to display Pointer<MyStruct> contents as intuitively as regular Dart objects. The outcome: seamless, crash-free inspection of native memory during development
Mentors: Student: Yash Hosalli
While working with real-time systems, I observed that Flutter DevTools provides detailed visibility for HTTP requests but lacks support for persistent protocols like WebSockets. Once a connection is established, developers have little to no insight into message flow, latency, or connection lifecycle, making debugging significantly harder. This project aims to address that gap by extending the Dart SDK (dart:io, dart:developer, and the VM Service) to capture WebSocket frame-level and connection-level data. This data will then be integrated into the DevTools Network panel, following the existing HTTP profiling model to ensure consistency and minimal overhead. The implementation will include WebSocket instrumentation in dart:io, exposure of profiling data via the VM Service, and UI integration in DevTools to display messages, sizes, latency, and lifecycle events. If time permits, the same architecture will be extended to support gRPC traffic. By the end of the project, developers will be able to inspect WebSocket communication in DevTools with the same clarity and usability as HTTP, significantly improving debugging for real-time applications.
Mentors: Student: Hassnaa Mohamed Ahmed
Extend ffigen to support C++, enabling Dart developers to use C++ libraries without manual wrappers. The project simplifies integration, reduces errors, and improves productivity by automating the process and providing a seamless developer experience.
Mentors: Student: Javad Asadi
The Dart and Flutter IntelliJ plugins rely on persistent WebSocket connections to communicate with the Dart VM Service and the Dart Tooling Daemon. The current implementation uses the Weberknecht WebSocket library, which does not properly handle WebSocket ping/pong control frames. In environments with antivirus software idle connections may be terminated, causing debugging sessions and tooling communication to disconnect unexpectedly. This project proposes migrating the WebSocket transport used by the Java VM service client to the modern WebSocket implementation available in the Java standard library. The migration will update the connection and message transport logic while preserving the existing VM service protocol. The deliverables include the new transport implementation, integration into both the Dart and Flutter IntelliJ plugins, removal of Weberknecht dependencies, and validation across common development workflows.
Mentors: Student: M. Fazri Nizar
This project proposes an experimental Android-specific backend for package:webcrypto that replaces the bundled BoringSSL native library with calls to Android's built-in Java Cryptography Architecture (JCA), accessed through package:jnigen. The current BoringSSL/FFI backend ships an approximately 300-500 KB native library per ABI. A JCA backend eliminates this binary overhead entirely by using cryptographic providers already present in the Android runtime. The project will implement Dart wrappers for all Web Crypto primitives (digest, HMAC, AES-GCM/CBC/CTR, RSA, ECDSA, ECDH, HKDF, PBKDF2) behind the existing webcrypto platform interface, with full conformance testing against the BoringSSL backend. A working sample project already demonstrates the approach for P0 primitives (SHA-1/256/384/512, HMAC, AES-GCM) with statistical benchmarks across 7 Android devices showing JCA is 7-29x faster for hashing at large payloads while BoringSSL retains advantages for AES-GCM. Deliverables include the complete JCA backend on an experimental branch, a performance analysis report with binary size comparison, documentation, and a migration guide.