Looking for pilot users
I created a tool for software teams that integrates a bug submission button (similar to Intercom-style chat buttons) directly within your team's product. The idea is to let product owners, QA and other team members submit bug reports (that include screenshots and screen recordings) from within your own product while it's running in a testing environment. I'm looking for teams that can take part in a pilot. If you're interested, let me know in the replies or reach out to me at ravi@development.kitchen .
Hey there. Had a quick play of the demo. Looks good.
Just a quick thing if you could restrict the default screenshot view to the current window without the tabs, that might make users less anxious in terms of privacy, etc.
Cheers
Thanks for taking a look, and thanks for the feedback. Restricting to just the current tab definitely does make sense. The reason this can't be done at the moment is a technical one but I'm hoping that will change soon. Curiously, some have suggested the ability to record outside the tab is useful in capturing some bugs and behavior. But it would be great to give the option to users integrating to restrict this.
If you are interested in the technical reasons: the screenshot and screen recording features rely on recent additions to WebRTC in browsers that allow capturing the screen and recording it. That dialog to select the screen/app/tab is presented by the browser as part of the WebRTC API - it's the browser's own UI. Unfortunately, they don't allow restricting what display surfaces are shown in that selection dialog. I hope this will change soon because the ability to allow restricting the surfaces is in the spec (which is itself still not final at the moment) but the implementations in browsers just hasn't caught up from what I can see. Technically, there is another way to implement screenshots in the browser but that requires users install a browser extension.
Yeah I hear you. Its not a showstopper for sure. Just something that made me pause. In an office environment where test teams are using your tool, the privacy concern may not be that much of a... concern. The tester would/should be focused on the testing task and would not be looking at anything NSFW or private.
Some feature suggestions (they are probably already on your roadmap but...)
JIRA integration would be good. i.e. rather than (only) building your bug tracking tool, integrate with widely available ones. JIRA probably exposes APIs (would make sense but I'm not sure). Automatically upload your video of bug captured, create a new issue, etc. (Zendesk, etc).
Slack integration as well. Not a big user of slack but its all the rage now. So defo a must.
Consider building this for mobile as well. Thats probably a V2 feature and has other challenges but would be nice for mobile devs as well.
When you're building your payments flow on your website checkout consider using BankPayments.net. Its great alternative to PayPal (and much cheaper as well). Disclosure: I'm the founder of BankPayments.net.
Cheers
These are great suggestions, and echo what I've heard from others. Integration with issue trackers is in the works. And as you guessed, doing something like this for mobile is a significant feature set so it will be further out. But definitely something others have suggested. Thanks for the suggestions! I will keep BankPayments in mind when it comes time to start building a payments flow (my first thought was Stripe here).
Ok cool. I knew you'd have thought of these features as well since they tie in with what many people would probably want from this. Keep at it, I think theres something here. I've had remote teams working for me (in my real life) and me having to video a bug that they couldn't reproduce themselves manually was definitely a pain.
Great that you'll consider BankPayments.net. We are positioning ourselves an alternative to PayPal not Stripe (although we are significantly cheaper than both!). As you know most sites offer both Stripe and PayPal in their checkouts. You can offer all 3 including us. Just gives the customer choice.
With BankPayments.net imagine a payment flow like PayPal but where your customer uses their familiar Online Banking login rather than having to pre-register with PayPal (and you pay less). We can give you a demo when you're building your payments page. Let us know.
Example costs (at current UK prices for the services):
For a £100 payment you collect from your Customers
For a £1000 payment you collect from your Customers
I'm sure you get my point :)
Cheers.
Are you using Open Banking for this? Just some thoughts after taking a quick look at the landing page: for payments, trust is obviously important. If you are using Open Banking and are regulated as a TPP, noting that would definitely help establish trust. Also this might be my developer mindset but when I've considered payment platform integration in the past, looking at API docs is one of the first things I do. I don't see any while I'm not signed up (not sure if they're available after you sign up).
In the meantime, if you are still using remote devs or have a dev team and would find it useful to submit bugs with screenshots and recordings, let me know if you are interested in being part of a pilot group. Mostly, I am looking to talk briefly once in a while to see if and how it's addressing your issues and if it can do more.
Thanks for the feedback! We'll look at adding more info to the landing page, its still a WIP (we launched last week). For the Dev API docs I completely agree as well. But we haven't found any decent API documentation writing tools. Most of the ones we have found require some special markup that you have to learn to get things formatted the way you want (lifes too short to learn another markup language). Ideally we'd want a WebFloweque tool where the formatting is all WYSIWYG. We're still searching.
Yes we still use the remote team for our other project. Thats winding down in a bit though. However this is on mobiles. Android specifically. As mentioned previously it was a real pain-point for me to video a phone with another phone whilst trying to reproduce the bug! :) I'm sure others would have experienced that as well. So mobile support for V2 would be great.
Oh... and one more use for your tool I've thought of. Not only for tracking/reporting bugs but also for capturing proof that a feature has been completed before the build is delivered to the tester/client. Something that can be monitored by a PM.
With the remote team, I used to ask that "Dev testing evidence" of completed features was attached to the Trello tickets when they marked them as "Done". Before this they used to mark tickets as Done but when I got the build the bug was still there (they had clearly not tested it). Providing Dev testing evidence is pretty standard but not something they were familiar with. Quality improved dramatically.
Anyway using your tool, they could have attached videos to the ticket showing them performing the user journey i.e. clicking through the buttons to show the new functionality working instead of screenshots as testing evidence.
I somehow missed this comment earlier, this is a great idea, a little mini story demo, I'll think about how to incorporate this in, thanks
No worries... getting that co-founder gold for free is what IH is all about :)