The app currently provides a TUI and CLI interface. However, users might want a GUI or web interface.
Currently, the backend and UI logic is largely separated, though some coupling still exists. This feature would mostly require implementing a GUI which is asynchronous and exists in its own thread, and the core event loop could be heavily inspired by the current TUI implementation.
The main issue blocking the GUI implementation is a lack of experience and knowledge about the options Rust provides for this problem - however, no such issues should block a web interface, besides the time needed to implement the functionality.
The main considerations would be to resolve #9, #10, to provide a seamless experience.
The app currently provides a TUI and CLI interface. However, users might want a GUI or web interface.
Currently, the backend and UI logic is largely separated, though some coupling still exists. This feature would mostly require implementing a GUI which is asynchronous and exists in its own thread, and the core event loop could be heavily inspired by the current TUI implementation.
The main issue blocking the GUI implementation is a lack of experience and knowledge about the options Rust provides for this problem - however, no such issues should block a web interface, besides the time needed to implement the functionality.
The main considerations would be to resolve #9, #10, to provide a seamless experience.