Why openweb projects fail

I have been developing and using #opensource and #openweb projects for nearly 40 years. For the last 20 years at the coalface of development, this is my experience.

Most #openweb projects are more than 99.9% unusable this is normal. A few come up to 5% usability; these are the “successful” ones. It’s very rare for a project like mastodon to be 50% useable – but more than 90% of the people I push in that direction still bounce – though this is more likely because of digital drug habits of the #dotcons than the UX of the project which is good itself.

Let’s be generous our #indymedia reboot project is currently 90% unusable; this is normal for openweb projects. It’s hard to build something with limited resources and training.

Our plan is to make it as simple and #KISS looking as possible to roll out to small groups of testers to develop it into being 20% useable by their feedback. While doing this we can roll out the idea of the project to bring more energy and resources into this shift from 10% to 20% usability.

We only open outreach when we are beyond that 20% level, because it would obviously be self-defeating otherwise. Then inch up the usability while shifting the social expectations of good #UX to a social harmony.

UPDATE:

If you would like to help with this process please set up a account here  https://unite.openworlds.info/indymedia/epicyon/issues and give us feedback on this test site https://indymedia.openworlds.info and this test look and feel template https://indymediadev.openworlds.info/test-css/ two versions of the UX then add an issue to the unite site with your feedback for the developers.


Discover more from Hamish Campbell

Subscribe to get the latest posts sent to your email.

2 thoughts on “Why openweb projects fail

Leave a Reply

Only people in my network can comment.