Bugsee allows developers to see what led to bugs and crashes in live apps and eliminates the difficult, time-consuming task of bug and crash reporting.
@perpetuous Sergey, do you mind being the beta tester for these? Send me and email to finik@bugsee.com and you will be one of the first to know when we have something to show. Cheers!
This is awesome, been looking for an alternative to Crashlytics since Twitter sold it to Google. Very happy that an independent solution is out there 🔥
Has anyone here installed it? Would be cool to hear about the SDK's effect on app performance and stability.
@sebfeed Thanks, Sebastian. We hear this sentiment quite often. As for your question, yes, we have many customers live in the app store. Some of them were kind enough to comment above. Here is example, an email we received yesterday from one of our customers Jamie D.
Thanks for hunting us @hnshah!
Hi Product Hunters, this is Alex from Bugsee.
We’re stoked to be here today, so we’re offering a Product Hunt exclusive 30% discount to anyone who signs up today (no credit card required).
Bugsee is a bug and crash reporting tool for iOS and Android apps. Like a black box on an airplane, Bugsee locally records everything that the app is doing. Whenever a bug occurs, everything you need to debug has already been recorded and available in an easy to view format:
- Video of user’s actions + touch events (including in live apps)
- Network traffic (including body)
- Console logs (including print in swift on iOS10)
- And so much more…
Also, last month, CrashProbe — the ultimate benchmark for mobile crash reporters — named Bugsee as the #1 crash reporter for iOS — http://www.crashprobe.com/ios/
Technical stuff about Bugsee:
- Added with just one line of code
- Increases the app size by ~300KB
- Passes all App Store certifications (uses only public APIs)
- Does not slow down the UI of a live app
- Secure fields are obstructed in the video recording
- Does not stream, while requiring only ~4MB of local storage
- Has a negligible impact on battery life
- Documentation: https://docs.bugsee.com/
- Fully functional demo: https://www.bugsee.com/demo (no signup required)
Hope to hear from you all on how we can improve Bugsee.
Thank you!
PS: If you’re interested in one (or more) of our stickers — let me know and I’ll ship them to you right away https://twitter.com/BugseeHQ/sta...
PPS: If you’re curious about Bugsee’s backstory, here it is https://medium.com/@fishman/my-c...
Report
@fishmanalex Video capture has been a very helpful feature for diagnosing and managing bug reports. Thanks for building a great product and sharing your insights along the way!
@fishmanalex I can't wait to try this out! Non-iOS devs have no idea what a pain point remote debugging is. For example, here is our latest crash report from "the other guys": #788 - Foundation - _NSErrnoMessage. And yes, that is the entire message. Video is a game changer, really excited for this.
@flighthack Hi Vladislav. Glad you like the logo. Yes, Cordova/PhoneGap is definitely supported (see https://docs.bugsee.com/sdk/cord... for more info). We work with React Native applications as well. Let me know if you have any questions or need help integrating with your app.
A class dump shows that the iOS SDK borrows significant code from PLCrashReporter, protobuf-c, and HockeySDK... In some cases changing the copied class name (i.e. BugseePLCrashReport).
It seems that at best, consumers of the Bugsee SDK will be violating the license agreements for the above software packages, and at worst this seems to be outright code theft. Am I overlooking anything?
@sergiokrawchuk Hi, Sergio. Thank you for your comment. PLCrashReporter is pretty much the industry golden standard for implementing crash reporting, it is open source, has a very permissive license and is used by pretty much every SDK and app implementing crash reporting capabilities. In order to prevent collisions in linkage between different SDKs and let them coexist, PLC even has a built-in "namespace" mechanism for prefixing all the functions at built time, that is exactly what is used in prefixing all the functions with "Bugsee". protobuf has Apache license and is distributed as part of PLC. If there are any license violations we would be happy to look into them and fix asap, feel free to contact me personally at finik@bugsee.com or @finikk if you have any other concerns.
Report
Thanks for this, I liked it really, one question tho,
what it's main difference from something like "https://instabug.com" ?
@ahmgeek Thanks Ahmad. Instabug does in-app bug by recording some static data and screenshot and letting the user draw on it. Bugsee is conceptually different, it gives the developer much more context, it shows him how user got to that screen in the first place. It records video of the last minute, touches, network traffic with headers and body, all console logs, system traces, etc. Bugsee web player allows developers to replay all of these in a synchronized manner. Most importantly, when user sees a bug, he doesn't need to reproduce it again, or try to remember the steps he took to get to this state, he just reports, everything has been already recorded for him! This makes a huge difference, and saves hours for users, testers and developers.
Bugsee
Bugsee
Bugsee
StriveSDK for iOS
Bugsee
StriveSDK for iOS
Bugsee
StriveSDK for iOS
Bugsee
Bugsee
Bugsee
Bugsee
PromptPlays.ai
Flystein
Bugsee
MailKing by cloudHQ
Bugsee
Bugsee
Bugsee
Bugsee