Vuestic UI experimental

[asvae]

Right now the development is mostly "just going". We don't have defined goals. We don't have a good way to prioritise our work.

This approach has its cons:

• We might be (and probably already are!) spending a lot of time on things that are not useful.
• We don't have a good vision of next steps and all steps seem equally important (testing, new features, blog, community etc).

I suggest a following plan to pivot the development to make it more predictable:

• First thing - we stabilise current release. It shouldn't be perfect, but it has to be robust enough to allow for new features (which doesn't seem to be the case, based on the number of recent regression bugs). This would allow us to keep trust with existing userbase.
• We decide on experimental project and move on with it. Experimental project could be a cool feature, that is not present in other frameworks. It could be videos or articles. It could be whatever you can think of, but it has to have a metric of success (number of start, number of posts, number of contact form usage). It should also be limited by a timeframe (2 weeks to month seems fair for me). Experimental version won't have polish or docs and would be prototype rather than working implementation.
• If experimental project is a success - we integrate it into core, adding all polish and documentation. If it doesn't - we scrap it and proceed with next experimental project.

Idea is to shift from "developing something" to "experimenting with new ideas, then going forward with whatever works best". We will still keep resources for community support and bug fixes, but about 20% of development resources could be enough for that for now.

Let's keep this post comments to gather ideas for experimental development.

[asvae]

• 3750 - a way for user to create their own component from our composables

• Techical blog posts
• AI interface builder