If you started a site that advocated for, say, jumping rope as exercise, 10 out of thousands of visitors might go pick up a jump rope. You’re providing something that the vast majority of visitors don’t need.
If you want a higher adoption rate, either:
- solve an acute problem - something that many visitors woke up thinking they need to do today.
- come up with a specific compelling reason/use for a timeline. Not app features, but things I can do with a timeline - solve a problem. Focus on the strongest one. Dumb example: maybe the best use of a timeline you can think of is for someone to put it their resume or applicant portfolio. Once you’ve picked one or two, if you actually believe they’re compelling, focus on those.
- or get much more targeted visitors, like only those few people who are actively looking to create a timeline.
We built this product as an experiment to document experiences in a much easier way than writing a blogpost.People who are not interested in blogging could tell a cohesive story by stitching a set of posts which are easier to understand.
We are trying to experiment this and see if it could be used as a microblogging tool for experiences and stories as an alternative to writing a blogpost.
We will surely reflect on your feedback but if you have anything that we could look to pivot can be helpful for us to consider from here on.
thanks again
Is this something you and your friends eagerly want and constantly use? I.e. that you and your friends would use if you weren't working on this startup, and had merely come across it as potential users? If so, you should be able to get users from among your friends and their friends. And if not, it's a made-up idea (http://paulgraham.com/startupideas.html) that you can't expect to fix by tweaking it.
My guess is it's the latter. This sounds like a made-up idea to me.