231–240 of 240 posts
Earlier quoted context omitted.
Professionally I do all of my development in Firefox and only occasionally check that Chrome works
It seems pretty bold move when you consider that V8-based browsers covers 75.5% of the market [1]. [1]: https://gs.statcounter.com/browser-market-share
That said, this looks outstanding, it could really be a great option for QA teams.
Earlier quoted context omitted.
Or, some users might have hidden the taskbar, or the clock. Or have several screens, and only one of them has the clock...
Users that might customise their system a bit by digging into the settings are usually more inclined to give a detailed report in case they encounter a bug or have a general knowledge of what to look for when requested for some information in my team's experience. Sounds much more like an edge case.
I think SAML should be available for business tier as well.
I'll draft a PR to put them on the SSO wall of shame at https://sso.tax/ when I'm at a laptop
Earlier quoted context omitted.
I am building a version of this that lets you store the data on your computer, you can export it and send it to your team (manually) so you can use any data hosting you want. Let me know if you're interested!
I'd also be interested, at least for internal bug reports and such. From what I can see, jam.dev is collecting what I collect for dev-teams anyhow, just faster and more comprehensive. But this would possibly move customer data in requests and screenshots out of our control, and the entire hassle of adding subcontractors and managing order data processing agreements have taken quite a few good monitoring and debugging…
Earlier quoted context omitted.
Firefox on Android too, though probably ~nobody uses that.
I do!
Earlier quoted context omitted.
Agree, it's a debugging tool for what users see, and users see your app on WebKit in Safari. So agree, the PdM should not be using Chrome. I suggested the Kagi Orion path elsewhere in this comment page too, since that would give the PdM extensions, while still seeing what users see.
Man. It will literally never stop being funny to me when people try guilt-tripping developers into adding Safari support. It's the exact same shtick, every single time: "Can we have Firefox support? It would really help promote the Open Web." "Sure, it was on our roadmap already." "AKTLY You need to rewrite your app for Safari support and WebKit coverage because if you ignore that then imagine how bad the iOS experie…
Developers might not like it but people use it. Personally I use it for almost everything now.
Earlier quoted context omitted.
I think they serve different purposes. Sentry/Bugsnag etc track code errors and exception . But sometimes for an user an error is not a code exception, but the software having the wrong behaviour. Some examples: > "The button brings me to the wrong page" > "I filled out the whole form but the submit button is not enabled" > "The video should autoplay but is stuck loading" Those things do not show up in Sentry logs.
Sentry has session replay that should catch all of these things - it doesn't look any higher friction than this tool.
This tool allows the reporter to select when data should be collected
Looks like 'large free plan' includes 25 jams. I was able to make only 10 or so jams (I could have deleted some jams but no more than 2 or 3) and now I have to 'Upgrade'.