-
Notifications
You must be signed in to change notification settings - Fork 2.6k
[EN] Feedback for: /fundamentals/index.html #1173
Comments
Its based on where the users are. If you are on mobile you expect a good On Sun, 22 Mar 2015 15:18 bobgasink notifications@github.com wrote:
|
|
We are saying users cant find content as well on non-optimised sites Your impression that mobile sites hide content that desktop shows If you only care about desktop users and traffic from search on desktop On Sun, 22 Mar 2015 15:49 bobgasink notifications@github.com wrote:
|
On 3/22/2015 8:49 AM, bobgasink wrote:
I am so pleased to see this question opened up again. I only joined but wasn't able to do so, since that thread had already been closed Even though GitHub is described in the documentation as being for This issue is important enough to me that I want now to take a moment I too received an email from Google claiming that my web pages "have Like ArtistScope, who initiated the #1087 thread, and bobgasink who In my case, there's the added rub that I have been trying for several In Google's manual on Web design fundamentals, to which I was directed
<
But the reality is quite different: when I do let content dictate E.g., the 3 "critical mobile usability errors" for which my 3 website http://roses.communicatingbydesign.com/news/RosesNews.html http://roses.communicatingbydesign.com/ToC.html http://roses.communicatingbydesign.com/FYI_cancer-and-the-retail-economy.html were cited are:
This is ridiculous. If visitors using mobile phones can't be bothered There are plenty of other visitors who value this website's original And ArtistScope raised another relevant concern in the earlier #1087
I couldn't agree more, and have recently documented one instance of http://she-philosopher.org/home/technical/BrowserProblems.html (currently configured as a beta test site, ergo off-limits to the big Thankfully, I've reached the point where I no longer care whether But I object strenuously when Google Search -- which has proven Deborah |
@phronimos this is the problem, the lack of understanding of why it is important to cater for users across all form factors. You are forcing users to zoom in on your content on a mobile device. Google search has always been about giving users the best result at the best time, and if users can't easily read your content, it is not the best result. You mention
These are 3 issues that users on mobile hate the most. Content that they are forced to pan around on and zoom, content they can't read correctly due to font sizing issues and links that they can't click. Un-happy users means less time on site, less click's through to other content and less chance they will convert (if you take payments). Just to reiterate, if you don't want to make your content work well on mobile, that is perfectly fine. The search changes only affect your site for users who are using mobile devices (which is a huge number). |
|
I'm closing and locking this issue. You've demonstrated several times now that you don't understand the issues that user's face or even how to build sites that work across device form factors by stating: "What they don't want is separate applications which have different, or harder to use, or dumbed-down oversimplified interfaces." - this is exactly what we are not saying, you choose to think it is. Pinning multi-device issues down as a "stylistic site" is not what is happening in the industry nor what we are saying. What you are saying is the equivalent of saying "I won't make my site accessible for screen readers because it's a stylistic choice"
Sigh You've just negated your previous arguments and thrown in a baseless accusation for the need to go mobile. |
Way too many "mobile" versions of applications are dumbed-down and nearly useless. Often there is so little screen left between big sloppy borders that it's like looking at the world through a mail slot. THIS WHOLE GOOGLE POLICY IS MISGUIDED!!!!!
The text was updated successfully, but these errors were encountered: