Subscribe
Sign in
Shake Crash Reports — Personalized crash reporting for mobile apps
Turn your app crashes into relationship-building opportunities with your users, prevent bad reviews & fix issues fast. Personalized crash reporting harvests the power of data: Automatically see affected users, stack traces, screen recordings, network logs etc.
51
Replies
Best
Robin
Hey ?makers! Love Shake for bug reporting (not yet a client). I think it would be very valuable if you would do a walkthrough video of Shake (how does it look like on mobile, what can the user see, frontend etc.). All the best and thanks a lot!
p.s. @petechats Do you offer any discount for product hunters? Would be awesome!
Report
Share
Heeeey @robinkunz . Awwww it's always nice to get a message like this.
Regarding a video walkthrough - you're spot on! We definitely miss it, and we're already working on it.
Regarding the discount - great question again. We offer Shake Crashes for free to everyone actually! And regarding our other product for ticket reporting, today we don't offer any discounts apart from the one for the annual commitment.
Congrats on the launch! How does the crash reporting work exactly? How does it contact the application's team?
Hey @rubenwolff! After Shake SDK is integrated in the application, crash reporting is enabled and necessary mapping files for the build are uploaded, crashes that happen in the application will appear under Crashes section on Shake Dashboard. Let me know if you have any further questions, I'd be happy to help!
@rubenwolff Currently you can search through grouped crashes on Shake's Dashboard, but we are working hard to integrate our crash reporting with 3rd party services like Jira, Trello, Asana and others, so once crash arrives at Shake's Dashboard it gets forwarded to other service immediately ;)
Hi Peter, this looks like a great product. Would the crash reports also catch a ‘soft crash’ such as app restarts, memory leaks etc.?
@jordanh we appreciate your question — yes, indeed it will and will report it back to you. Just as an example, here's the truncated list of exceptions & errors Shake Android SDK catches:
- IllegalArgumentException
- IllegalStateException
- IndexOutOfBoundsException
- NullPointerException
- StackOverflowError
- OutOfMemoryError
etc.
Our dev and QA teams *really* spent a ton of time developing and testing these and it works like a charm.
If you'd like to try it out, don't hesitate to start chatting with us on our website through that chat bubble — we'll assist, guide and support you and your team as much as needed.
Congrats on your successful launch yesterday - this could be so useful for us after beta! :) Greenr does climate calculations and is featured today - wanna check us out? 🌱
@gabrielle_bourret_sicotte of course! Thanks for trying to make our world greenr :)
@gabrielle_bourret_sicotte also a tip for your team: Check out the 2nd product on our app insight platform: https://www.producthunt.com/post... as it's made for alpha development stage too, while you're testing the app internally. Good luck with the launch afterwards 👏
An integration with Smartlook Qualitative Analytics would be nice to see what went wrong.
@sebastian_potcher go figure, thanks for the idea! Our product team lives and dies by user feedback so we've actually added your feature request directly to our Public Roadmap https://feedback.shakebugs.com/i..., let's see whether others would be interested too.
And a tip: In the meantime you can always use our Zapier integration 🔗 www.shakebugs.com/integrations
Heeeey everyone, it’s me again, Shake’s founder.
After a successful launch of our *bug and feedback* reporting tool for apps 1 year ago, we’ve been working hard on the next chapter in our product roadmap - *crash* reporting. We’re beyond excited to share it with all of you today.
We believe crash reporting (just like feedback reporting) should be personal. Shake Crash reports don’t focus on *statistics and charts* - instead, it’s focused on your customer's *experience* with your app right after it crashes in front of their eyes.
Shake Crash reports now complement our existing feedback reporting product, allowing your app users to share feedback after a fatal crash has occurred. All while the useful data is being collected in the background.
Shake Crash reports help app development, QA and product teams to:
- Automatically see why a crash occurred, to who precisely, its stack trace, environment and steps to reproduce it.
- Receive additional information with every crash: screen recording and user feedback.
- See crash events automatically grouped into an actionable list of issues on the web Dashboard.
A big shout out to everyone that made this all possible. Couldn’t be more proud today! ❤️
wow, active user of shakebugs, amazing product and super cool team. looking forward to implement crash reporting too.
@divyanshunegi Glad to have you onboard! Thanks so much for the kind words.
Hi Peter & Team! I love the idea to turn such a “painful” user experience like an app crash into something useful for both parties. Just trying to understand from a user perspective - when will this (maybe personalized) crash notification be shown? upon next app open event?
@simon_3 precisely, you got it right! (Or, you can optionally turn that crash notification *off* and still continue receiving data-rich crash reports without interrupting your app users. You choose.)
Great idea, great product!
Hoping that you have taken into account the user's privacy during the recording of the app UI: for example by replacing sensitive inputs with some "*".
@photobook_cam thanks, we appreciate it. Your hopes are not in vain 🤣 Shake SDK indeed offers a ton of ways to get rid of any Personally Identifiable Information before sending the ticket from your app: www.shakebugs.com/docs/android/m...
- you can mark any app View as Private
- you can get rid of touch events from the logs
- obfuscate sensitive parts of Network requests and/or responses
etc.
Good luck with Photobook!
Thank you!
I really appreciate the different ways you allow app Developer to take into account final users privacy.
Had awesome time working on this! We are very proud how this came out.
We made Shake Crash Reports with the goal to help teams get to the bottom of every crash. We've even used Shake to debug Shake "WAAAATT?!"
Hope you all enjoy it and looking forward to hearing your feedback :)
I work in quality assurance, and pride myself on being a perfectionist. That being said, I love this tool; it will make your work a lot easier!
@millerboyz999 the brief answer is that with Shake you also get:
• a video of what happened before the crash
• comments from app users and testers describing in their words what happened
• *automatically* attached steps-to-reproduce (logs, network traffic, notifications on a timeline)
• collaboration with your team - assign, prioritize and leave notes on received crashes in one place
and all of that helps you to fix your crashes WAAAY FASTER than before! Make sure to try it out for free and let us know if you maybe disagree 👌 — our Product team is constantly listening to user feedback and improving Shake.
@thea_mark thanks, we appreciate it — tbh it feels good to launch it after many months of meticulous development 👩💻
@pierrickleclerc Indeed, and keep those users happy! That's how great relationships get built.
Thanks for that. And let them know they can always get in touch with us via that chat bubble on our website 💬
@emremigh cheers, we hope it'll help you too avoid all the bad reviews :)
