What about cookies session ?

Please Describe The Problem To Be Solved

I'd like to request the addition of a Cookies management system to the Flet project. The current version of Flet does not have a Cookies management system, which could greatly enhance the functionality and user experience of the app.

Cookies are small data files that are stored on a user's device and can be used to remember user preferences, login credentials, and other important information. By implementing a Cookies management system in the project, you can provide users with a more seamless and personalized experience, while also improving the security of their data.

The Flutter documentation on the Cookie class (https://api.flutter.dev/flutter/dart-io/Cookie-class.html) provides a comprehensive guide on how to work with Cookies in Flutter. You could use Cookies to remember a user's preferred language or currency, store login credentials, and track user behavior and preferences.

Adding a Cookies management system to Flet could help improve user satisfaction and potentially even increase revenue.

(Optional): Suggest A Solution

The preferred solution is to implement a Cookies management system that uses the Cookie class in Flutter. The system would allow users to store their login credentials, preferences, and other important information using Cookies. The implementation details would involve:

Creating a new class that handles the creation, reading, and deletion of Cookies.
Adding a user interface to allow users to manage their Cookies preferences.
Ensuring that the Cookies management system is secure and compliant with privacy regulations.
Tradeoffs in design decisions include balancing the level of user control with the level of automation, and determining which types of data to store in Cookies.

Thank you for considering this feature request.

No Flet files or tests are named; start with the linked Flutter Cookie class documentation and establish the feature's supported platforms and session scope. Done would require an agreed cookie lifecycle, preference controls, privacy and security requirements, and tests covering the supported targets.