191–200 of 240 posts
Earlier quoted context omitted.
Orion could make this easier - basically a Safari fork with Chrome / FF plugin support (use it as my daily driver, pretty good and uBlock Origin in Safari? Yes please!)
Consumer facing stuff so nobody in my use case is running much other than a few versions of Safari or Chrome on desktop or really Safari on mobile. (87-92% iOS on mobile)
Earlier quoted context omitted.
It would be great to have a FAQ page on your site mentioning this. I was on your docs page and did a search for "firefox" as well as "safari" in the search box and there were no hits at all. Seems like something that people would often be checking for.
Great feedback, that would definitely be a good thing to add!
We've noticed many tool devs think everyone uses Chrome (because those devs got non tech people in their social circle to install Chrome so "everyone they know" uses Chrome), but users who don't know devs just use whatever's there, and that means iPad, iPhone, and most Mac "end users" are Safari.
Along with being needed for those users, any tool that looks this good and works this magically is also going to appeal to dev teams that can appreciate why users like iPhones and designers like Macs, those teams will want this to work in Safari too.
That said, if you couldn't readily support Safari, I wonder if your extension could be adapted to work in Kagi's Orion browser that supports Chrome and Firefox extensions (to an extent), while being based on WebKit. Perhaps that's a path that could allow webkit debugging.
We would definitely pay for a Safari extension to be installed from Apple app store for each of our UX devs, product managers, and canary users.
For enterprise deployment, it needs to come from Apple app store or be distributed as an installable package through an automation mechanism. MAS (Mac app store) is easiest.
The extension needs to either be free, or have a "full price" version, so that it can be licensed per seat/user through corporate volume purchasing to run on employee devices. The way managed devices work, there's no way for companies to pay for employees to use in-app purchases (IAP).
Earlier quoted context omitted.
Consumer facing stuff so nobody in my use case is running much other than a few versions of Safari or Chrome on desktop or really Safari on mobile. (87-92% iOS on mobile)
Yeah sure but this is tool for internal use
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.
[0] https://tailscale.com/blog/sso-tax-cut
[1] https://sso.tax/
Jam is a browser extension that allows you to create the perfect bug report in just one click. You will now be able to capture an instant replay of the bug happening on your web app and include all the developer logs required to cut your bug reporting time by 20x.
(to me that was a more useful summary)
> It’s actually really hard as a non-engineer to file useful bug tickets for engineers... So the engineer would be frustrated, I would be frustrated While I have been in this scenario before, saying something along the lines of, "If I don't get 100% bug reports, I can't do 100% bug fixes," 9 years of experience and maturity later: no, I wouldn't use this. It wouldn't engender me more respect, power or efficacy in the…
That's all well and good, but even a halfway engaged PM is going to play with the product while it's in development, and they will tell you about what they discover along the way. It may not strictly be their job but they're going to do it. If a tool exists to help them capture more information that makes their inevitable reports more useful, is that a bad thing?
I got really excited before I saw there was no firefox support. Thats a deal breaker for my team :( I really like this idea and if Firefox support was added I would purchase it in a heartbeat.
[I work at Jam] We do have an internal build for Firefox.. it's coming :)