Live data from Hacker News

Ask HN: Feedback on my startup

news.ycombinator.com

31–40 of 45 posts

Re: Ask HN: Feedback on my startup

#31
post #5
post #4

I wish there was a bit more information to be honest. Is this a patching system? Or is it just like an alert system for updates? I'm not really sure what it is.

Sorry, the site is a bit broad at the moment (will fix). It's to post new features and product updates in one place. The idea is to replace changelogs, product update emails/blog posts, and release notes.

If you do emails please, please, PLEASE! - include the name of the product and a brief description of what it does as a bit of a reminder when you send out the email form of your updates.

My absolute biggest pet peeve with changelog emails is that they just say "Hey I'm Tony from Initech and we just added a new feature to BigBoomBlaster!!". I'm sorry who is Tony, why do I care, why did I care when I signed up for this list, what does this product do? What is an Initech?

I sign up to a lot of things, I need that taster of information to remember which of the 30 things I signed up to this week is emailing me without a hint as to who they are. No the domain name doesn't count, I didn't even read it when I signed up. The product already got me hooked enough to sign up for this thing, just remind me what it is and I'm all ears.

Re: Ask HN: Feedback on my startup

#32
I like your page, good minimalism. Also, I like the why you handled branding. I got a good feel of the talent behind the scene. But there are couple of things you need to take care. Some are critical too.

The main thing as everyone spotted you required a good short description. It's better to put a short description just below the message about the problem that you are trying to solve. for example, if you take basecamp landing page, they give more focus to the heading - “Work together the easy way”. Just after that, they had a short description about the problem they solve - “Basecamp’s unique blend of tools is everything any team needs to stay on the same page about whatever they’re working on. There’s nothing else like it!”. From this, I got a gist of what basecamp do.

Once you add the short description, bring the early access button to upfront. Then it makes sense. It will be like in an order message, short description and call to action. check this http://i.imgur.com/vUxKt5B.png I made small modification on your web page.

Another thing I like to say is about the timeline. For me, When I saw it in first glance, I felt it as a screenshot of actual product. But I later got confused. it seems more like a design that you added for aesthetic because inside the timeline slice there is no text saying like for example “Release 1.0.5” instead a green rectangle. If it's an actual screenshot make it a bit more intuitive. It's just a suggestion.

If possible, try to add a bit more drilled down information on page scrolling. Because sometimes people require a bit more details. for example, you can refer basecamp website. On the website as you scroll more details information starts coming and make more sense to the app. Even you are in early access stage but still you require some more supporting descriptions. Which helps you to get more clicks from your target audience.

Also, I suggest putting your address/country. Becuase I like to know where are you from? :). Nice to see a lot of energy. All the best to your team.

Peace

Re: Ask HN: Feedback on my startup

#33
I love the design and the "Get early access" button, especially the minimalism involved in the side bar. However, I do have a question on the site's functionality, if it's meant to provide a singular place for product updates, changelogs and emails, how does it differ from Atlassian's JIRA?

Re: Ask HN: Feedback on my startup

#34
It's a good, clean design, but the page doesn't make it clear what your product does. To be honest, I'm guessing it's road map / change log as a service based on the name more than anything. So assuming I'm right in what productmap does, you've definitely got a good name :)

Re: Ask HN: Feedback on my startup

#35

It's a good, clean design, but the page doesn't make it clear what your product does. To be honest, I'm guessing it's road map / change log as a service based on the name more than anything. So assuming I'm right in what productmap does, you've definitely got a good name :)

Thank you. That seems to be the feedback here (page isn't clear enough). Considering you run a service, how do you convey tell your users about new features in an engaging way?

Re: Ask HN: Feedback on my startup

#36

I like your page, good minimalism. Also, I like the why you handled branding. I got a good feel of the talent behind the scene. But there are couple of things you need to take care. Some are critical too. The main thing as everyone spotted you required a good short description. It's better to put a short description just below the message about the problem that you are trying to solve. for example, if you take baseca…

Thank you! Super helpful feedback. I'll add a second like explaining the problem this solves (replacing release notes, changelogs, etc.)

I'm from Toronto :)

Re: Ask HN: Feedback on my startup

#37
post #35

It's a good, clean design, but the page doesn't make it clear what your product does. To be honest, I'm guessing it's road map / change log as a service based on the name more than anything. So assuming I'm right in what productmap does, you've definitely got a good name :)

Thank you. That seems to be the feedback here (page isn't clear enough). Considering you run a service, how do you convey tell your users about new features in an engaging way?

At the moment I don't have a defined way of updating users of new features. As I'm aiming to run BugMuncher as openly and transparently as possible, a public road map has been on my todo list for quite a while. I'm very interested in your product, which brings me to my next bit of feedback:

I clicked the 'Get Early Access' button, and it opened what looked like it was going to be a survey, which put me off. I decided to give you the benefit of the doubt and clicked the 'Start' button, but my initial instincts where correct, and there where 8 survey questions to answer. I'll be honest, at that point I closed the tab and went about my day.

I'm BugMuncher's solo-founder and only employee, so all tasks fall to me, this makes me really value my time, to the point where those survey questions where enough to make me move on.

When someone clicks the early access button you should do nothing but capture their email address, so you can keep them updated and notify when beta access is granted. Once I've started using your product I'll be much more receptive to the survey.

Re: Ask HN: Feedback on my startup

#38
post #3
post #2

My first reaction: Is this something that companies actually want/need? Have you validated the market? That's ultimately more important than the v0 landing page design.

You're right. I have talked to a handful (<10) of potential customers already. They're willing to try it out and going to share with them over the course of the next week.

Does try out mean actually pay money for though?

Re: Ask HN: Feedback on my startup

#39
post #35

Earlier quoted context omitted.

Thank you. That seems to be the feedback here (page isn't clear enough). Considering you run a service, how do you convey tell your users about new features in an engaging way?

At the moment I don't have a defined way of updating users of new features. As I'm aiming to run BugMuncher as openly and transparently as possible, a public road map has been on my todo list for quite a while. I'm very interested in your product, which brings me to my next bit of feedback: I clicked the 'Get Early Access' button, and it opened what looked like it was going to be a survey, which put me off. I decided…

Appreciate the honesty here! I'll make sure to shorten that down to 1-2 Qs.

Re: Ask HN: Feedback on my startup

#40

I love the design and the "Get early access" button, especially the minimalism involved in the side bar. However, I do have a question on the site's functionality, if it's meant to provide a singular place for product updates, changelogs and emails, how does it differ from Atlassian's JIRA?

Thanks :) I think Jira is more for managing the sdlc and an internal tool.

The focus here would be to have an intuitive interface for product updates and getting feedback on new product decisions.

Post reply on HN