Hacker News new | ask | show | jobs
by okgabr 3788 days ago
Instabug's other cofounder here.

Wow, that does sound frustrating and I'm sorry we let you down. I thought we did enough to communicate those changes, but obviously that wasn't the case. This is a learning experience for us and we'll definitely do better next time. But let me explain the things we did do, because I'm not sure yet how the information didn't reach you.

We've been reacting very quickly (as fast as we could) to this. And we've even applied some of the changes that you've asked for on the same launch day. And this is the way we treat our users in general. We do our best to react fast their requests.

We've made sure to document all the changes (even the statuses) in our blog post. We've sent it to all our users and placed it inside the dashboard to make sure everyone knows what changed and why it changed. What do you think would have been a better way to notify you?

Also, we didn't mean to be protective! On the contrary, we'd love to get your feedback. What would you like to know?

We got the crash reporting disable question more than once and we've added it to our SDK FAQs a few months ago (https://instabug.com/developers).

Anyways, we're truly sorry to disappoint you. And I'd be more than happy to explore a solution for the statuses changes issue, and also let me know if there's anything else we can do to make it up to you.

1 comments

How far in advance do you believe you notified your users?
The main change in v3.0 was that we moved the custom statuses into tags. We thought that would be a good idea to automate the workflow and make use of the tags given it's agility. We did the migration but we didn't think it'll break anyone's workflow. That's why we didn't think that we should notify anyone before launching, and that was our mistake. We explained the logic behind the change after we launched but we should have done that before we launched.
To;dr: they didn't.