Do not get me wrong, i have nothing against making the OS simpler, easier to consume to everybody, i am just against the way you propose and against the way you communicate it. It feels like in your head Haiku already became some corporate entity which have to grow, inclusive scraping the bottom of the barrel.
Changes in user group is inevitable, but i need somebody to draw me an optimistic picture how the focus-change from developers to users can positively affect the development progress of the OS, without using the keywords diversity, inclusivity and other fancy words.
You are referring to users as “customers”, which extends the meaning of the word “user” in a specific way: the customer is entitled for support, while the user is not. I fear this is dangerous path and it should be discussed before the project takes it.
I am getting worried because this culture change in the Haiku user group. It feels like corporation-isation, pushing responsibility to others, a switch from hobby to serious work.
-/-
It feels like you would like to use Haiku as a main OS, but presumably you are not satisfied with the peace or the level of the development (or both) and you see the “getting Haiku popular” way as a solution to get more workforce into the project to get (your) user experience better which is basically the" let somebody else fix it for me", which was never a winner strategy, as it means losing control over the solution. Instead of trying to popularize the OS to get your issues fixed you could try to cut out the unnecessary part and fix the system yourself for yourself. This can result in a thriving community, not just a stagnating one where everybody have ideas but not enough developers to implement them.
-/-
I would like to think about Haiku like a source of enjoyment, a fruit of passionate work instead of a mundane work and i would like to see creative users, not entitled customers. From my point of view this is a big philosophical difference.