How makers stay productive

took a look. not going to be an in-depth review but I get the use-case!

1) So, my questions are, what are you opinion on Bugshare?

It's a clean app and I see it being very useful for teams (whether remote or on-site) and especially during on-boarding. Imagine your first week at a company trying to understand why the app isn't working locally for you.

You might want to look into becoming an app integrated with confluence/notion or whatever tools companies are using for wikis these days as that is a good growth hack.

OR work with Sentry and catch errors and send them to your app where you can do your tracking and note-taking.

2. Assuming you're a solo developer, when you run into an issue, would a tool like Bugshare be useful for you?

As a solo developer, most of the issues I run across are quick syntax errors that I don't need to Google or Stack Overflow to fix.

3) What would be your usecase for Bugshare? (e.g. Some people use it to log how they fixed a bug, so they never forget if it comes up again).

As a solo developer, the extension would probably be helpful when I run across a bug on an open source project and don't want to dig through the issues on github to see how to work around the issue. Or to find a fork that is more up-to-date and has addressed the issue.

** other notes ** I didn't see JavaScript as a supported language.

Sent my feedback via the live chat form the other day: glad to hear it was a misunderstanding of the core purpose of the app.

I must've been sleepy when I wrote the feedback, because I get it now! It definitely makes sense for smaller teams, although I'm curious how you plan to differentiate with a good ol' wiki.

When I face bugs I don't want my team to face, I just write them in a wiki.

@malcolmtyson has great feedback, particularly on the part of catching errors: integrating with something like Sentry would be great and I see some next steps being perhaps building not just an extension but a web frontend for adding data proactively.

2) Assuming you're a solo developer, when you run into an issue, would a tool like Bugshare be useful for you?

No, but that's not the purpose of the app, no? It's a tool for teams. Perhaps if there was a public, global community similar to StackOverflow on your app it'd make sense for solo devs. It could even make great demo.

Actually, I double down on that last bit. Make a public, global community accessible.

3) What would be your usecase for Bugshare? (e.g. Some people use it to log how they fixed a bug, so they never forget if it comes up again).

Do see my feedback on wikis.

Best of luck building this! I hope my feedback serves.

I was initially confused about what it does (it's like your own StackOverflow right?). Figured after reading Malcolm comment.

I think it seems more like a team tool? Or is there a public database that you give me suggestions from?

I usually personally avoid browser extensions, but who knows. If this is accurate and fast, why not.

Hey, feedback from a UX engineer with a background in product research.

1) So, my questions are, what are you opinion on Bugshare?

Just ask this after your target user already use your product. It's a product not an illustration. If isn't the case you are asking about your marketing in general to random people.

2) Assuming you're a solo developer, when you run into an issue, would a tool like Bugshare be useful for you?

• "Assuming you're…" People are either something or they are not. To assume is to invent realities.

• Never, never, never, never… ask "Would…" that only opens the door for people to think about potential (not real) situations. And that's not what you need.

You need facts. And every little detail about your target that can give you context about their situation.

On the problem side (in-depth conversations with your target):

• How do they actually solve the problem that you solve?
• Are they paying for a product to solve it?
• Are they actually using that product?

On the solution side (testing and analysis)

• Do you have traffic to your marketing efforts?
• Conversions?
• Are they buying from you?
• Actual use of the product?

3) What would be your usecase for Bugshare? (e.g. Some people use it to log how they fixed a bug, so they never forget if it comes up again).

Again… "would". This type of things need to be discovered asking people how they solve their problems in real life. Don't give ideas.

If you want, take a look at this short FREE ebook from Kevin Dewalt: Beginning Customer Development

Hope it helps :)

1. instead of creating the landing page, just go straight to the web app where people can read what bugshare is doing to share knowledge of bug fixing.

2. whatever people share or post, on that Q&A specific topic. Will it index on google search engine? so answers can be found when i search on google and it can redirect to the main site bugshare.

3. Improve your lighthouse of bugshare.io is much needed to make it faster and more accessible to developers to search some topics.

4. currently, i have to log in to see all the knowledge, can i not log in and see what other bug related topics? If i want to answer, then i will log in.

5. you can find some categorize bugshare topic based on the tech stack.