2012-12-06

The Long List of Google+ Issues


This started as a looong Google+ comment.

Android app still sucks. Here is why: (long list)
Apart from the already mentioned things it has major issues with notifications and bad networks.

Like you clicking on a notification about a new comment... And it silently fails, showing just the comments it already loaded, not informing you that there are a dozen other ones it failed to load.

Why can't you add additional circles to share a posting with after it's posted?

And of cause that notification is gone forever once clicked.
No matter if it actually succeeded in loading the content you are being notified about.
... So much for transactions.

Notifications between multiple Android devices and the web (with the Nexus7 and 10 tablet usage grew even stronger)

Why is there still no Google+ for GoogleTV?
It's so image centric that it's unusable for reading the texts on tablets (the background image has higher priority then the few bytes of comments), yet it needs to be sideloaded=pirated for the big screen of a GoogleTV.

And images not being zomable in the web?
The larger your physical screen is, the less you are able to read text in images.

Having to log out and in In the Android client all the time because it does notify only for that one account and one page?
What's the point of having e.g. a GoogleTV or a tablet that's shared between people? People having work and private accounts! Discouraging the Businesses that spend tons of money in Google advertisement and want to work "on social". Be agile. React fast to follower comments and posts!

Still no API!
Not a single multi-protocol twitter client can integrate Google+ and give people a smooth way to move over by cross posting for a while, their posts becoming longer and more image-heavy then Twitter allows and finally leaving Twitter for Google+.
Your competitor is Twitter, not so much Facebook!

There is not even an account and page selector in the "share with" activity of the Google Plus app.
Very bad user experience. 
You have to select and download and type content again because you suddenly notice that your Google+ app is currently in the Page instead of the account or the personal instead of some after-dark account.

What's the issue with *Nicknames*?
I can't find people that I have known for years because I know them by their nicknames. I have no clue and I don't care about their "real names".
They don't want me to know their real name and for good reason!
PS: in the Android contacts app it doesn't fine people when I search for their nickname entered in gmail-web as "nickname: _____" in addition to their real name that I don't know from the top of my head because I only use it for paper-mail and door-bells.

*Image ordering*!

The ability to *add additional images* to your last post. Not making all images you could possibly need, then typing, then sending, then finding out you are missing one but only being able to edit the text.
(It's already an improvement that you can edit texts you entered on the phone in the web. Previously they turned up empty when you hit "edit".)

Why isn't *Blogger* better integrated into Google+ ?
Google+ is microblogging, Blogger is (macro)blogging.
I can inform people here about a blog-post but I can't turn a microblog-posting that gets too long into a full blog post.
I *can't copy&paste* because all + and # will be removed from the text, garbling the text beyond recognition!

Don't get me started on how poorly practucally all Google Android software is tested on slow and unreliable networks.

Every Twitter client stores a posting you send and *retries* until it can upload. Google+ doesn't. It forces you to keep the Google+ client open, thus highjacking your phone until network stabilizes enough to send out the posting.

Edit the posting you just sent due to a type? The one that's still in memory?
You have to load it from the network again!

When you use multi-signin on the web and select menu->link to this post?
It keeps the /0/ and /1/ in your link. So you can't jsut paste that link anywhere because if this happens to be your work account /1/, people clicking that link will get a login screen instead of the posting.

The Google+ web site fails terribly when Ajax responses are login-pages injected by hotspots you're passing by. It doesn't retry and you have to load all that heavy, bandwidth eating imagery again! While not a bug in Google+ it is becomming very common and should be dealt with in error handling code soon.

Oh and there is no reasonable place to give bug reports like these...


Kommentar veröffentlichen