app.convertri.com - Firefox is unsupported browser

[digitarald]

URL: https://app.convertri.com/

Browser / Version: Firefox 75.0 Operating System: Mac OS X 10.15 Tested Another Browser: No

Problem type: Site is not usable Description: Firefox blocked Steps to Reproduce: (I only saw this reported via twitter but I wanted to make sure we track this as chrome-only site and attempt outreach to learn about what's blocking them)

Browser Configuration

• gfx.webrender.all: false
• gfx.webrender.blob-images: true
• gfx.webrender.enabled: true
• image.mem.shared: true
• buildID: 20200224094751
• channel: nightly
• hasTouchScreen: false
• mixed active content blocked: false
• mixed passive content blocked: false
• tracking content blocked: false

View console log messages

From webcompat.com with ❤️

[softvision-oana-arbuzov]

Thank for the report. Unfortunately, a special account is needed to sign in.

Taking in consideration the provided screenshot, I'll move it to Needsdiagnosis for further investigation.

If the reporter (or anyone else) can provide more information (test account, register account link), please add it here.

[digitarald]

Unfortunately, a special account is needed to sign in.

Trial seems to be free: https://app.convertri.com/signup

[karlcow]

https://app.convertri.com/assets/moved-manager.min.js?v=2020-02-26-12-12-19

  if (!a()) {
    t.otherwise('/chrome-only');
    return
  };

  function a() {
    var t = window.navigator.vendor,
    e = window.navigator.userAgent;
    return (n() && 'Google Inc.' === t && (!r() && !a() && !o()));
    function n() {
      return !!window.chrome
    };
    function r() {
      return - 1 !== e.indexOf('OPR')
    };
    function a() {
      return - 1 !== e.indexOf('Edge')
    };
    function o() {
      return !!e.match('CriOS')
    }
  }

This is done right at the start, through

angular.element(document).ready(function () {
    angular.bootstrap(document, [
        'convertri'
    ],{
        strictDi: true
    });
});

agressive user agent sniffing. a simple ua override will not solve the thing. and probably they should be contacted to understand whey they felt the nedd to do that.

[karlcow]

@digitarald it would be cool if you could approach them.

[digitarald]

@karlcow I don't have a contact; but maybe pinging on twitter helps.

[karlcow]

contact us page https://www.convertri.com/about

The CEO @avfletch but i don't think he has been around much.

[avfletch]

Hi, I'm Andy Fletcher, Founder of Convertri :)

Thanks for bringing this to my attention @karlcow.

I'm flattered that we've got enough traction for amazing teams like this one to be discussing us. I figured the least I could do is come and share the history of how we got to this point, even though I'm confident you guys probably won't like the conclusion :)

We founded Convertri in January 2016 on a shoe string budget. I put ~$100k of my own money into the company to give us ~6 months of run way to get to a v1 launch.

After 3 months it became clear that some things were going to have to give so we took some tough choices. One of which was dropping cross browser support. At the time this felt like a massive technical failure but given the choice was that or not ship on time, needs must. We figured we'd launch Chrome only then circle back and pick up the other browsers post launch (or be dead if the thing flopped!).

Fast forward to July 2016, where we organised a big affiliate driven launch event that lasted a week. During which we sold over 2,000 people on the software.

It was at this point we discovered something we didn't fully appreciate about our target market. Marketers use Chrome.

2,000 units sold and we received 3, count 'em three, complaints to our support desk about only supporting Chrome.

To start with we figured this was just a byproduct of people being frustrated and refunding. We offer a very liberal 30 day, no questions asked refund policy.

So we went through every support ticket. We went through the user agent on all our logs. And sure, there were a few more but most people who encountered the "Sorry, it's Chrome only" screen obviously already had it or were happy to go download it.

Now we're 4 years in. We've got a few hundred thousand lines of Javascript, a lot of it horribly dated and based on AngularJS (yes, I can feel your hatred through the internet) and the economics continue to push us in other directions.

Cross browser compatibility remains an item on our "How can we acquire more customers?" list but every time we look at where we can put technical effort the expected uplift from making it work with Firefox, Safari etc just pales in comparison to other options available to us.

tl;dr - I'm flattered you are willing to reach out and see what's blocking us but sadly what's blocking us is us. Short of you coming to work for us for a couple of months for no charge, it's on us to fix and that's probably not happening any time soon :)

[karlcow]

@avfletch Andy thanks for the context. One comment and one question.

Marketers use Chrome.

Probably, and this is a chicken and egg issue. Basically by not allowing some users to fully experience with another browser, we self-select the target. So the stats just reflects what the entrance criteria was, a bit like of "there's no 70cm high child on this roller coaster, when the entrance criteria was more than 110cm". That said I understand the business priorities.

Cross browser compatibility remains an item

So that's the interesting question/comment here for Mozilla, which could help us.

1. what were the issues?
2. if removing the current user agent sniffing to block everything but chrome, does it still break in today's firefox nightly (76)?

Now we're 4 years in.

A lot of things have changed since.

The gap analysis usually helps us to understand and set our priorities for businesses like yours, so we can see what is missing.

[avfletch]

@karlcow - We don't just have stats of people using the app, we have the stats of the people that view the sales page, which works on any browser.

what were the issues?

That was a long time ago! I seem to recall it mostly being CSS issues but I'd be lying if I said I was sure.

if removing the current user agent sniffing to block everything but chrome, does it still break in today's firefox nightly (76)?

I'll have a go at this soon and find out for you. Does it have to be the nightly or would whatever the latest general release is be fine?

[karlcow]

I'll have a go at this soon and find out for you. Does it have to be the nightly or would whatever the latest general release is be fine?

@avfletch The latest general release is fine. And thanks this is awesome.

[softvision-oana-arbuzov]

The issue is fixed, "Sign In" page loads now.

Tested with: Browser / Version: Firefox Nightly 98.0a1 (2022-01-11) Operating System: Mac OS Monterey v.12.1, Windows 10 Pro

Closing the issue.

[softvision-oana-arbuzov]

@digitarald can you still reproduce it on your side?