21–30 of 31 posts
Earlier quoted context omitted.
I agree. The landing page isn't the nicest one. I'm not a designer, though, and I'd rather spend that time improving the product. Is there anything you'd like to see in the extension that'd convince you to pay for it? Happy to improve!
> anything you'd like to see in the extension that'd convince you to pay for it? Different pricing scheme, at least in the beginning. While $39 (or even $59) is acceptable as one time payment, I am not sure if I am willing to pay this for a product that's been on the market for only 3 weeks and whose future is unknown. Charging something like $1-$2 per month will earn you more in the long term and will provide a safe…
About pricing, I don't think that model would be better. As a solo developer, it's better to charge more and provide better support to fewer customers. I'm not saying no, but it seems to be working well for now. Thank you for the suggestions!
Earlier quoted context omitted.
I agree. The landing page isn't the nicest one. I'm not a designer, though, and I'd rather spend that time improving the product. Is there anything you'd like to see in the extension that'd convince you to pay for it? Happy to improve!
we developers are a stingy lot. I wouldn't base any pricing decision on what technical/developers say. The ultimate customer for this is a support person who is going to give feedback to a developer. To them and/or a QA team, you could be saving them a ton of time with this product. Consider that birdeatsbug starts at free for personal use and then $39/month. You might actually be leaving money on the table if you go…
Can i see a report somewhere?
When you are extracting logs, it creates a single archive with all the items you selected. Usually, it'll be: 1. Combined logs - everything in a single file 2. Network logs 3. Console logs 4. User interactions 5. Navigation events
One user already suggested it'd be nice to include generated HTML with more human-readable logs. I thought about having a web-based log reader, but this seems to be an even better idea.
May I suggest adding Jira integration?
This seems to be aimed at developers / testers but it might be useful for end-users too. If a customer reports a problem we can’t reproduce, it would be handy to just direct them to a plugin they can download to generate a report. But the up-front pricing model doesn’t work for that kind of scenario because customers wouldn’t pay for it. It would be better to have the customer download it for free and enter a one-tim…
I do recognize that this tool seems like it's oriented toward logic bugs whereas Sentry really shines in the unforseen outcomes case, but I'd bet a well placed "send feedback" link could still capture the browser details and breadcrumbs without requiring a formal error per se
This looks awesome. Is the underlying recorded data available in an easy to parse format like JSON? Would be quite powerful to do 90% of the work of transforming that recording to a puppeteer script to add to one’s test suite. Speaking of which, what is the state of the art right now for browser automation scripts?
Thank you! And yes, it's all JSON. It's not super easy to read when you get all the data this way, though. I'm planning to add a web-based log reader to parse the logs and display them in the same way it's done in the extension. Also, generating Cypress/Puppeteer/Playwright tests is on my to-do list. It should be fairly easy because all the data, including selectors, is already there. I wrote more about my plans here…
Can i see a report somewhere?
Sure, https://www.dropbox.com/s/zffejt4u2l5d3x1/logs-1620070042074... When you are extracting logs, it creates a single archive with all the items you selected. Usually, it'll be: 1. Combined logs - everything in a single file 2. Network logs 3. Console logs 4. User interactions 5. Navigation events One user already suggested it'd be nice to include generated HTML with more human-readable logs. I thought about having…
Earlier quoted context omitted.
Thank you! And yes, it's all JSON. It's not super easy to read when you get all the data this way, though. I'm planning to add a web-based log reader to parse the logs and display them in the same way it's done in the extension. Also, generating Cypress/Puppeteer/Playwright tests is on my to-do list. It should be fairly easy because all the data, including selectors, is already there. I wrote more about my plans here…
Hi, just to chip in because I read your request for feedback and also because I'm interested in seeing what Monito can do. I’ve been heading QA depts at large tech companies for a while now, and part of my job is to be up to speed with the latest tools and trends, and to write automation tools for various tech stack layers. To answer your question, my preferred front-end tool at the moment is Playwright (via C# bindi…