I’m wondering what kinds of technical changes would need to happen to enable mobile plugin support, or even to enable development of separate mobile plugins. Not a task-by-task breakdown, but more “at a high level, we would need to change how mobile renders XYZ so this is deprioritized because of ABC/waiting on ABC.”
I am not familiar enough with the differences between the desktop client and the mobile client to make a well-informed Feature Request, nor to contribute to this yet, but I would be really interested in supporting this work. My goal with this question is to learn more so that I can propose a coherent FR.
(My specific example, this is not the question I am trying to ask but is context) I would really love to be able to use SmartBlocks on mobile, or at least have them render as a viewable button even if they aren’t fully featured. I don’t know if that’s something I could contribute to on the SmartBlocks side or if that is impossible due to a Logseq specific implementation.
Ok cool, thank you! So to summarize, sounds like mobile plugin support would need to be enabled explicitly by Logseq, and they intend to do so after releasing their plugin component system? Do you know how I could follow development on that project?
Any idea if there might be a way to use un-optimized plugins?