Subscribe
Sign in
p/bugbattleAffordable In-App Bug Reporting for Apps and Websites
Start new thread
Lukas Böhler

Bugbattle 2.0 - The fastest and easiest way to report and fix bugs.

by
Bugbattle accelerates the bug reporting process at every stage of your app, website or industrial application.
🔎 Complete insights into bug reports
đŸ§© Integrations into your favorite tools
✅ Saves you a lot of time
We can’t wait to hear what you think.

Add a comment

Replies

Best
Pian Istien
Nice. Are you sure you do not required user consent to make the video recording? Apple took down some app because of this. And smartlook developed a consent sdk for this purpose SmartlookConsentSDK
Lukas Böhler
Maker
@pian_istien hey :) thank's for your comment! yeah - but our video recording is still in closed beta and will launch in the first quarter of next year :) We do some pretty nice stuff to avoid getting taken down or requiring permissions.
Lukas Böhler
Maker
Hi everybody, I am Lukas, founder of Bugbattle đŸ™‹â€â™‚ïž. We are super excited to share the product we’ve been building over the past few years with you all. Developing apps and websites ourselves at BoehlerBrothers, our software agency in Austria, we wasted a lot of time and nerves on battling bugs internally as well as in our collaborations with customers. Basic contextual details were missing from bug reports, such as information on the testing device, what android or iOS version the smartphone was running on or which browser testers were using. Our PM team would spend hours collecting feedback and packing all the infos together with screenshots into Jira and Notion tickets. After facing the same struggles time and time again and failing to find an existing solution to solve our problems (because they either did not provide the right features or were simply too expensive), we started building our own in-app bug reporting tool 🐞. After all, we are developers ourselves. This is how Bugbattle was born. Bugbattle automatically lets users take screenshots of a bug by shaking their device, then lets them mark it and send it to a developer without ever leaving the app or website. You developers then receive the bug as a ticket in your Bugbattle dashboard with all the important metadata such as console logs, session data and steps to reproduce. You can also integrate Bugbattle into your existing Jira or Trello boards and have tickets created for you in your PM tool of choice. Our CTO Niklas has written a Blogpost on our launch if you’d like to find out more. It is our dream to empower developers to spend less time on debugging and focus on the more beautiful things in a developer’s life. Check it out, and let us know what you think! 👋 Me and my team will be hanging out in this thread for a while if you have questions or feedback for us. Best, Lukas
Eduardo Moreno
Awsome idea, I've been playing around with https://wiredash.io but unfortunately it's flutter-only. This could be a great alternative for everything else. Congrats!
Lukas Böhler
Maker
@aguilaair_tech Hey Eduardo :) thanks for your comment! Our Flutter SDK will be ready pretty soon (within the next few days), so def. stay tuned. Would be awesome to hear your feedback!
Max Prilutskiy
Very nice idea! 💯
Lukas Böhler
Maker
@prilutskiy Hey Max, thank‘s for your comment! Would love to see how Bugbattle could speed up your testing flow @ Typeform 🚀 If you have any questions or would love a demo, just let me know 😊
Fredric Cliver
I was looking for the alternative of Instabug. That service charge for every each features. I couldn't understand it for the mini-size team and product. And found it and looks simple and excellent to achieve user feedback.
Lukas Böhler
Maker
Hey @fredriccliver, thanks for your feedback! We tried to be as fair as possible in terms of pricing - in addition we are trying to focus on the essentials. If there is anything missing within Bugbattle, don't hesitate to contact us, we are open for any feedback :)
John G.
Hi there, this looks really interesting. Is there a video that shows what it looks like from a back-end and then front-end experience on a website? Your videos above are pretty short and I'd like to see what is required, say just adding a line of code to insert a JS back-end and then what would the user see on the page where the JS has been inserted, do they just use the site as usual or do they need to click on something to start the session? Thanks, John