[abstractbeliefs]

"Currently, the app isn’t open source, as I felt it didn’t need to be."

No open source, not selling me as a customer.

If you make your entire product about customisation, you're doing me a disservice to not let me adjust the code as suits my needs, asides from the ethical position on free software.

[samrolken]

Not just that, but even:

> However, tools developed for Hollow will need to be open source to be approved

Weirdly contradictory.

[ryu-suke]

Another user point that as well, English is not my first language so i think i miss used the word 'approved', if a plugin is open source it will be labeled as verified otherwise it will be unverified, in both cases they will be available in the app's plugin section for installation.

[ryu-suke]

customizability lies in its plugin and theme system, not in modifying the core source code. The goal is to give users complete control over their experience without needing to edit the underlying codebase. You can create plugins to extend functionality, design themes to change its look and feel, and tweak everything to fit your workflow, yet i do understand how important for apps to be open source, therefore i wont guarantee that happening any time soon

[abstractbeliefs]

It's not one-or-the-other. You can achieve all that customisability without having to edit the code, while also leaving it as an option for those who want to take it further.