| name | test-flet-apps-dev |
| description | Use when testing or debugging Flet apps in maintainer/contributor development mode with local Python package sources and the local Flutter client, including web, desktop, browser, and computer-use verification workflows. |
Test Flet Apps In Dev Mode
Use this skill when validating a Flet app, example, feature, or bug fix against
this repo's local Python packages and/or local Flutter client during maintainer
or contributor work.
Core model
Flet dev-mode testing usually has one or two processes:
- A Python Flet app/server, run from
sdk/python.
- The local Flutter client, run from
client, when Dart/client or extension code
must be tested.
If only Python code changed, uv run flet run ... is often enough. If Dart,
Flutter, extension, or transport code changed, run the local Flutter client so
the changed Dart code is actually used.
The local Flutter client debug build uses a fixed app-server URL from
client/lib/main.dart:
if (kDebugMode) {
pageUrl = "http://localhost:8550";
}
Therefore, when using the local Flutter client without extra URL arguments,
start the Python app on port 8550.
Start the Python app
Run from {repo}/sdk/python:
uv run flet run -w -p 8550 examples/controls/core/interactive_viewer/handling_events/main.py
Adjust the sample path as needed. Use port 8550 when the local Flutter client
will connect with its default debug URL. Keep this process running and watch its
stdout for Python callback output, tracebacks, and event payloads.
For web-only checks with the packaged web client, open:
http://127.0.0.1:8550
Run the local Flutter client
