Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Why is Google search different on mobile Firefox compared to Chrome?

news.ycombinator.com

Post reply on HN
Print view View original

1–10 of 37 posts

Ask HN: Why is Google search different on mobile Firefox compared to Chrome?

#1

Post by 1drr »

For instance the Images tab is quite degraded and different in Firefox (Can't swipe picture), I also noticed that some widget apps like soccer matches are degraded. try typing "Barcelona matches" in both browsers and notice how degraded the matches widget is in Firefox compared to chrome (For instance the matches are clickable in Chrome but not in Firefox). There are other examples that I can't remember right now, I am sure of it.

I also noticed that AMP isn't available in Firefox, though I am not a fan of AMP, I still find it weird that it's not available, considering Google's motives behind AMP, which is to improve user experience, allegedly.

Isn't this a bit anti competitive and alarming?

Re: Ask HN: Why is Google search different on mobile Firefox compared to Chrome?

#6

Post by paulintrognon »

amelius wrote: post #3

> Isn't this a bit anti competitive and alarming? Never attribute to malice that which can be explained by laziness. (Variation on Hanlon's razor)

Well according to st3fan, "If you change the User Agent to Chrome you can see that it works pretty well on Firefox actually." That means that they removed features on firefox on purpuse right? Or does that just mean they implemented their feature "for chrome only", checking the user agent to make sure it works on chrome only?

https://news.ycombinator.com/item?id=20489237

Re: Ask HN: Why is Google search different on mobile Firefox compared to Chrome?

#7

Post by 1drr »

ggggtez wrote: post #2

>AMP isn't available on mobile firefox >it's Google's fault somehow Is this just begging for karma? There isn't even version or OS info. How is anyone going to actually discuss this other than just arguing blindly?

I created a new account to post this, so I have no interest in Karma.

It was just something that I noticed when I switched from mobile Chrome to Firefox. You don't have to discuss this blindly, just pull your phone and test for yourself, it'll only take you 2 seconds.

My phone has Android 8.0, Firefox Mobile 68.0

Re: Ask HN: Why is Google search different on mobile Firefox compared to Chrome?

#9

Post by dmitrygr »

paulintrognon wrote: post #6
amelius wrote: post #3

> Isn't this a bit anti competitive and alarming? Never attribute to malice that which can be explained by laziness. (Variation on Hanlon's razor)

Well according to st3fan, "If you change the User Agent to Chrome you can see that it works pretty well on Firefox actually." That means that they removed features on firefox on purpuse right? Or does that just mean they implemented their feature "for chrome only", checking the user agent to make sure it works on chrome only? https://news.ycombinator.com/item?id=20489237

Oftentimes a team at Google doesn't have the QA resources to test configuration X. In that case to avoid a potentially bad experience, feature Y is often gated to tested configs and and disabled for X, leaving X with the old experience since it had been tested on X.

Why does QA test only Chrome? Well if there is only enough QA time to test one browser, imagine having to be the guy to explain to the higher ups why it wasn't chrome.

Re: Ask HN: Why is Google search different on mobile Firefox compared to Chrome?

#10

Post by 1drr »

dmitrygr wrote: post #9
paulintrognon wrote: post #6

Earlier quoted context omitted.

Well according to st3fan, "If you change the User Agent to Chrome you can see that it works pretty well on Firefox actually." That means that they removed features on firefox on purpuse right? Or does that just mean they implemented their feature "for chrome only", checking the user agent to make sure it works on chrome only? https://news.ycombinator.com/item?id=20489237

Oftentimes a team at Google doesn't have the QA resources to test configuration X. In that case to avoid a potentially bad experience, feature Y is often gated to tested configs and and disabled for X, leaving X with the old experience since it had been tested on X. Why does QA test only Chrome? Well if there is only enough QA time to test one browser, imagine having to be the guy to explain to the higher ups why it…

I find it surprising that an organization the size of Google doesn't have the resources to test key features in such a notable browser.

Though I just searched and it seems Firefox has a shockingly low market share in mobile: https://en.wikipedia.org/wiki/Usage_share_of_web_browsers

Perhaps that's why it's not given the attention it needs, how unfortunate.

Post reply on HN