I really wish there is a way to show more than just the domain name next to the title.
>Good bye, Google Maps… thanks for all the fish (google.com)
is simply misleading.
>Good bye, Google Maps… thanks for all the fish (google.com)
is simply misleading.
I wish people would stop blogging on Google plus. Period.
It's the worst reading experience ever on the iPhone - nearly impossible as the text blurs, and you have to drag the article around to see it all and then wait for the blur to go away.
On Android, when I click one of these links it opens the app and the reading experience is very pleasant. Maybe I've just been spoiled, but I find the experience to be pretty good.
Edit: Also, I think it's kind of silly that you wish people would stop publicly posting on Google Plus due to your phone experience being subpar. I think the problem lies much more with you and your phone than it does with Google Plus as a writing platform.
(On the other hand, Tumblr looks great on mobile, and it doesn't need an app. Facebook, too, is at least readable on their mobile site.)
I was actually going to comment that I find G+ a great experience for these kinds of posts... oh well.
"It's your fault for not using the Google Plus App to view the page" is tantamount to saying, "It's your fault for not using IE6 to view the page."
You are, as the kids say, straight trippin'.
I was mostly asking if iOS had similar functionality, but it appears not.
But no, iPhone doesn't have that functionality.
Also, I thought it relevant to mention here that you can indeed read the post very clearly on the iPhone - but a seeming lack of this feature (Intents) in iOS makes this awkward.
(I'm not sure how they're detecting whether that hook is registered or not, though.)
Even just the ability to suppress the error message would be more or less fine.
But you're mistaken. I browse the web using a web browser. Even on my iPhone.
In my opinion, it's a far more elegant solution than encouraging developers to register pseudo-protocols to use in URLs that also result in very awkward interactions if the app's mobile site tries to redirect to the app and it is not installed. (Then again, this gives users a "choice" (!) of whether to open links or Intents in the mobile app or native app.)
Nope
On Android, when I click one of these links it opens the app and the reading experience is very pleasant. Maybe I've just been spoiled, but I find the experience to be pretty good.
This doesn't happen for me. I have a Galaxy Nexus with ICS, and I have Google+ installed and linked to my account, and this doesn't work - it opens the post in the browser. Is there some magic fairy dust that needs to be sprinkled into my microusb port for posts to be redirected to the Google+ app?
What's much worse, though, is that Google+ posts actually reliably crash the ICS chrome browser - as in 100% of the time. Whenever anyone posts anything on Google+, I have to open it in Firefox to read it.
Clearly Google needs to work on this.
Edit: Also, I think it's kind of silly that you wish people would stop publicly posting on Google Plus due to your phone experience being subpar. I think the problem lies much more with you and your phone than it does with Google Plus as a writing platform.
This isn't really that different than putting the post behind a paywall or some other inconvenient barrier to your audience. It might be a nice writing platform, but I think it's a pretty lousy reading platform.
The problem definitely lies with Google Plus as a web app. Whatever they're doing, it's just not a very good experience on a mobile device. Maybe on Android they redirect Google+ pages to their native app, but they don't even offer a way to do that for other platforms even if you have the native app installed (even a simple link on the page that opens it in the native app would be fine). It seems obvious that they're actively trying to promote their own platform over all other reading experiences, which is a radical departure from the ideals of the web that Google has historically cared about.
This is why I think every company should hire B and even a few C+ level talent. Someone has to do the boring details.
I think this is just a common Google problem; when you hire A+
level talent they don't want to spend their time adjusting css
for every platform.
In this case, Google plus as a blog, obviously all the platforms are targets. So the CSS should be adjusted for all the platforms, and that must be part of the specs. If you have A+ talent executing, either it will be done, or they haven't implemented that yet according to their priorities, or there is something more unknown to us.
Anyway, building a G+ app doesn't exactly require an extra 30 points of IQ and 5 years of school than making a web page display readable.
Maybe they should start using CSS brain teasers in their interviews, then.
If Google can't do simple HTML after all these years, there's something wrong.
In the case of Google+ that's the navigation bar.
Strangely, I could not trigger the issue when I was reading this post on my iPad. Now either Google has figured out the cause and found a workaround or the stars have somehow aligned correctly for it not to happen this time.
The following is a screen shot. Do you care to elaborate on what is wrong?
I also don't get any of the blur mentioned when scrolling.
While trying to do this, however, it just crashed Safari twice. I tried the same on my wife's 3GS, crashed Safari as well trying to read the Google Plus post.
Unfortunately I don't think there's anything we can do about Safari crashing while taking a screenshot at an inopportune time. Perhaps we can try to find someone on HN who works on at Apple?
At least on the Honeycomb tablet, can't talk about the mobile phones.
Reader parsed it fine and displayed it beautifully.
Yup, but it's probably the best writing experience for most bloggers, and also people who don't have blogs. Even if you have one with a decent readership, the engagement you get from Google+ is far higher than anything you can get when people need to use RSS and a reader to follow you.
OMG. Google is pulling a reverse-walled-garden.
Try the new-in-iOS5 "Reader" button in the URL bar.
However I'm a little worried about stealing what may be Google's content.
By the way, Hacker News is fairly unreadable on an iPhone because the text is so small text width so great. I haven't found a mobile interface that allows me to log in and comment.
I wish the same, but for different reason. I can't open Google+ links in office. :(
I was just about to write a Chrome extension to do this.
There is. I installed the user script Show Full Domain on Hacker News posts,
http://userscripts.org/scripts/show/121512
mentioned in an earlier Hacker News thread, and it works well. I knew the submitted article was from plus.google.com and was able to anticipate its content accordingly.
(I am running this user script on Chrome.)
https://chrome.google.com/webstore/category/home
For me it displays as (plus.google.com)
The Public Suffix List (publicsuffix.org) might be useful for this, although I doubt plus.google.com is listed in there (no same-origin security considerations). It's still the only systematic approach I know of that even remotely addresses the problem you're describing.
You're assuming he's using a device with a mouse. And why not add a simple feature that makes usability better on all platforms? Special case google plus here, just because this is such a common complaint. I've wanted it for a while, too.
I'm amazed that offering up a potential general solution that already exists, or suggesting someone measures their response before jumping at headlines, would result in downvotes here.
I think it's tone and missing the point. Starting a response with protip is a bit condescending, and the point isn't actually about not being able to use the UI to get the desired information, but about how the usability would be improved (for some users at least) by changing how information is presented.