12 ms·

[I work at Jam] We do have an internal build for Firefox.. it's coming :)

alt227 2y ago
Awesome, I will check back regularly. This looks like one of those tools that is genuinely really useful. I would love be able to tell my users to just fireup a browser extension and record a bug, rather than having to step them through how to capture all that data manually. Well Done! Bookmarking this page for the futuere: https://jam.dev/docs/downloads-and-browsers/browser-support https://jam.dev/docs/downloads-and-browsers/browser-support
- thedg 2y ago
  That’s so amazing to hear, thanks for the kind words
- deleted 2y ago
  [deleted]
mattl 2y ago
How about Safari? This would be very useful as not every developer has Apple hardware
- toekneestuck 2y ago
  Yes! Safari is also on the roadmap.
- jeffhuys 2y ago
  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!)
  - mattl 2y ago
    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)
    - jeffhuys 2y ago
      Yeah sure but this is tool for internal use
      - Terretta 2y ago
        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.
        mattl 2y ago
        But with a fork of WebKit? I don’t think another fork is all that helpful in the context of trying to fix a bug.
        Terretta 2y ago
        It's not a fork of WebKit. It uses WebKit. https://blog.kagi.com/orion-features https://blog.kagi.com/orion-features https://blog.kagi.com/orion-new-features https://blog.kagi.com/orion-new-features
        mattl 2y ago
        Ahhh. Someone said Safari fork but not WebKit fork. https://news.ycombinator.com/item?id=40323838 https://news.ycombinator.com/item?id=40323838
        talldayo 2y ago
        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 experience will be!!! People will blame you instead of themselves because they're simply too domesticated to fix technology issues, so do their work for them!" ...rinse and repeat for everything Apple refuses to support themselves. We wouldn't be begging people for Safari support if it was a successful browser or if people actually cared about it in the first place.
Yeroc 2y ago
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.
- thedg 2y ago
  Great feedback, that would definitely be a good thing to add!
  - Terretta 2y ago
    Love this tool, want to buy it for our team. Unfortunately, a tool that doesn't support Safari can't readily be used to help iterate products that use default browser or webkit webviews on MacOS or iOS. 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).
irrational 2y ago
That’s good to hear. I haven’t used Chrome since Firebug was released.

Awesome, I will check back regularly. This looks like one of those tools that is genuinely really useful. I would love be able to tell my users to just fireup a browser extension and record a bug, rather than having to step them through how to capture all that data manually. Well Done! Bookmarking this page for the futuere: https://jam.dev/docs/downloads-and-browsers/browser-support https://jam.dev/docs/downloads-and-browsers/browser-support

thedg 2y ago
That’s so amazing to hear, thanks for the kind words
deleted 2y ago
[deleted]

mattl 2y ago

How about Safari? This would be very useful as not every developer has Apple hardware

toekneestuck 2y ago
Yes! Safari is also on the roadmap.
jeffhuys 2y ago
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!)
- mattl 2y ago
  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)
  - jeffhuys 2y ago
    Yeah sure but this is tool for internal use
    - Terretta 2y ago
      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.
      - mattl 2y ago
        But with a fork of WebKit? I don’t think another fork is all that helpful in the context of trying to fix a bug.
        Terretta 2y ago
        It's not a fork of WebKit. It uses WebKit. https://blog.kagi.com/orion-features https://blog.kagi.com/orion-features https://blog.kagi.com/orion-new-features https://blog.kagi.com/orion-new-features
        mattl 2y ago
        Ahhh. Someone said Safari fork but not WebKit fork. https://news.ycombinator.com/item?id=40323838 https://news.ycombinator.com/item?id=40323838
      - talldayo 2y ago
        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 experience will be!!! People will blame you instead of themselves because they're simply too domesticated to fix technology issues, so do their work for them!" ...rinse and repeat for everything Apple refuses to support themselves. We wouldn't be begging people for Safari support if it was a successful browser or if people actually cared about it in the first place.

Yeroc 2y ago

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.

thedg 2y ago
Great feedback, that would definitely be a good thing to add!
- Terretta 2y ago
  Love this tool, want to buy it for our team. Unfortunately, a tool that doesn't support Safari can't readily be used to help iterate products that use default browser or webkit webviews on MacOS or iOS. 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).

irrational 2y ago

That’s good to hear. I haven’t used Chrome since Firebug was released.