3 ms·
I understand and I agree, I tried to spell it out as simply as possible and put the demos at the forefront for the project, but it's hard explaining a new appro
by chadillac 13y ago
I understand and I agree, I tried to spell it out as simply as possible and put the demos at the forefront for the project, but it's hard explaining a new approach to solve and old problem in a simple way without getting verbose.
I think I need a prettier demo with "tips" and "hints" about what exactly is different... 90% of people will click through the demo, see nothing they haven't seen before and move on, which is a shame.
- hownottowrite 13y agoYep, taking the complex and making it simple is never easy. Sometimes it's about dialing back on features. Sometimes it's about kittens. Don't get frustrated though. Take each opportunity as a chance to learn and experiment. I've often wondered what would happen if someone launched three identical projects on github with totally different approaches to marketing. I suppose one could compliance this with multiple versions of the README, but I'd go as far as testing different names too. I suspect some may see this as a heretical approach to open source development, but it's naive to think that any group of people are somehow resistant to marketing techniques. Anyway, the key is having a great product. Keep at it and eventually you'll be able to explain it in a single sentence that makes the concept instantly clear.