Replies: 6 comments 3 replies
|
For TV: It should be noted that for Android TV and even Tizen TV, it is inconvenient to operate through the interface, and a better TV solution is to only have a start-stop button, and then users can open the background management web interface through a QR code on the local network for configuration. |
|
For UI: The design on the graphical interface should first consider whether to use flutter controls completely or mix webview. If it is completely flutter controls, it needs to be consistent with the function of the web end. It is best to have a document to synchronize the design (the interface is different but the function is as close as possible). |
|
https://github.com/sky5454/picoclaw_fultter_ui This is my implementation, and I want to contribute it to the Picoclaw Repo, which is freely available for use by the PICOCLAW project. Just one small request: Please mention the first version contributed by my name Sky5454. |
|
❤️ Really appreciate the work! |
|
released at https://github.com/sipeed/picoclaw_fui/releases platform support: Android/Windows/macOS, and Linux/iOS is the next thing to do, |
|
How about wrapping an existing web UI into a lightweight cross-platform app with a system webview, like Wails? |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
[RFC] Adding Cross-Platform UI for Picoclaw
Overview
This discussion proposes adding a cross-platform UI interface for the Picoclaw project to improve user experience across multiple platforms. The goal is to provide a native-like experience while maintaining a single codebase.
Proposal
1. Technology Choice: Flutter
We propose using Flutter as the framework for building the cross-platform UI. The rationale behind this choice includes:
2. Supported Platforms
Target Platforms:
Rationale for platform selection:
These platforms cover the majority of our user base and provide a good balance between desktop and mobile experiences. We can expand to iOS and web in future phases based on user demand.
3. Android Minimum Version
Proposed Minimum Version: Android 10 (API Level 29)
Released: September 2019
4. UI Content
Modifications based on the current picoclaw-launcher
Open Questions
Open for Discussion:
Next Steps
Please share your thoughts, concerns, and suggestions! All feedback is welcome as we shape the future of Picoclaw's user interface.
All reactions