[Question] Future support for plugins/extensions or customization APIs?

Hi, I have been using Namida for almost a year now, and I really, really like this project. I can see myself continuing to use it for a long time. However, since Namida is currently difficult to build locally from source due to its custom dependencies and modified packages, many feature ideas or personal changes can only be brought up through issues instead of being implemented and tested by users themselves. Because of that, I wanted to ask whether there are any plans, or even just a possibility in the future, to support plugins, extensions, scripting, or some kind of customization API. The reason I ask is that some user needs can be quite personal or subjective. They may not be suitable as core feature requests, because different users may expect different behaviors from the same feature. For example, in my previous issue: - https://github.com/namidaco/namida-snapshots/issues/53 I mentioned the behavior of the shuffle/random playback option. My personal expectation was different from the current design: I expected that when a shuffle-like mode is enabled, pressing “next” would jump to a random item in the current queue while keeping the queue order unchanged. Then, if the playback mode is changed back to sequential playback, it could continue from the current position. I understand that this may not match Namida’s intended design, and I do not want to insist that this behavior should be added to the core app. There are also other examples of personal customization needs, such as: - floating / desktop lyrics on Windows or Android - custom playback behavior - UI layout adjustments - visual customization or small UI tweaks These kinds of features may be useful for some users, but not necessarily suitable for everyone. Because of that, I was wondering whether a plugin, extension, or scripting system could ever be considered for Namida. Such a system might allow users to implement personal customizations without increasing the maintenance burden of the main app or requiring every small preference to become a built-in feature. I fully understand that designing and maintaining a plugin API can be difficult, especially for a Flutter app and a project with complex playback features. So I am not asking for an immediate implementation. I just wanted to ask whether this direction is planned, possible, or completely out of scope. I also enjoy participating in the community around Namida and building related side projects, such as `DiWu17/namida_history_app`. If there is any suitable way to contribute to Namida or its ecosystem, I would be very happy to help. Thank you again for your work.