{"id":14739,"date":"2019-04-11T01:06:21","date_gmt":"2019-04-11T01:06:21","guid":{"rendered":"https:\/\/rsoftsolution.com\/blog\/with-consumer-g-dead-currents-hopes-to-make-waves-in-the-enterprise.html"},"modified":"2019-04-11T01:06:21","modified_gmt":"2019-04-11T01:06:21","slug":"with-consumer-g-dead-currents-hopes-to-make-waves-in-the-enterprise","status":"publish","type":"post","link":"https:\/\/www.rbsitsoftwaresolution.in\/blog\/with-consumer-g-dead-currents-hopes-to-make-waves-in-the-enterprise.html","title":{"rendered":"With consumer G+ dead, Currents hopes to make waves in the enterprise"},"content":{"rendered":"

Google <\/a> today announced<\/a> that Google+ in G Suite, the last remaining remnants of what was once Google\u2019s <\/a> attempt to rival Facebook and Twitter, will now be called Currents. We don\u2019t need to belabor the fact that Google+ was a flop and that its death was probably long overdue. We\u2019ve done that. Now it\u2019s time to look ahead and talk about what\u2019s next for Currents. To do that, I sat down with David Thacker, the VP of Product Management for G Suite, at Google\u2019s Cloud Next conference.<\/p>\n

As Thacker told me, Google has shifted its resources to have the former Google+ team focus on Currents instead. But before we get to what that teams plans to do, let\u2019s talk about the name first. Currents, after all, was also the name of the predecessor of Google Play Newsstand, the app that was the predecessor of the Google News app.<\/p>\n

\"\"<\/a>The official line is that \u201cCurrents\u201d is meant to evoke the flow of information. Thacker also noted that the team did a lot of research around the name and that it had \u201cvery low recognition.\u201d I guess that\u2019s fair. It also allows Google to reuse an old trademark without having to jump through too many hoops. Since the Google+ name obviously now carries some baggage, changing the name makes sense anyway. \u201cThe enterprise version is distinct and separate now and it was causing confusion among our customers,\u201d said Thacker.<\/p>\n

\u201cThis allows us to do new things and move much faster in the enterprise,\u201d Thacker explained. \u201cTo run a consumer social network at the scale of consumer G+ requires a lot of resources and efforts, as you can imagine. And that\u2019s partially the reason we decided to sunset that product, as we just didn\u2019t feel it was worth that investment given the user base on that. But it basically frees up that team to focus on the enterprise vision.\u201d<\/p>\n

Now, however, with consumer G+ gone, the company is going to invest in Currents. \u201cWe\u2019re moving consumer resources into the enterprise,\u201d he said.<\/p>\n

The plan here clearly isn\u2019t to just let Currents linger but to improve it for business users. And while Google has never publicly shared user numbers, Thacker argues that those businesses that do use it tend to use it expensively. The hope, though, surely, is to increase that number \u2014 whatever it may be \u2014 significantly over time. \u201cIf you look at our top G Suite customers, most of them use the product actively as a way to connect really broad organizations,\u201d Thacker said.<\/p>\n

Thacker also noted that this move now removes a lot of constraints since the team doesn\u2019t have to think about consumer features anymore. \u201cWhen Google+ was first designed, it was never designed for that [enterprise] use case, but organizations had the same need to break down silos and help spread ideas and knowledge in their company,\u201d Thacker explained. \u201cSo while Google+ didn\u2019t succeed as a consumer product, it will certainly live on in the enterprise.\u201d<\/p>\n

What will that future look like? As Thacker told me, the team started with revamping the posting workflow, which was heavily focused on image sharing, for example, which isn\u2019t exactly all that important in a business context.<\/p>\n

But there are other features the team is planning to launch, too, including better analytics. \u201cAnalytics is a really important part of it,\u201d said Thacker. \u201cWhen people are posting on Currents, whether it\u2019s executives trying to engage their employee base, they want to see how that\u2019s resonating. And so we built in some pretty rich analytics.\u201d<\/p>\n

The team also built a new set of administrative controls that help manage how organizations can control and manage their usage of Currents.<\/p>\n

Going forward then, we may actually see a bit of innovation in Currents \u2014 something that was sorely lacking from Google+ while it was lingering in limbo. Google Cloud\u2019s CEO Thomas Kurian told me that he wants to make collaboration one of his focus areas. Currents is an obvious fit there, and there are plenty of ways to integrate it with the rest of G Suite still.<\/p>\n

<\/a><\/p>\n

Article source: http:\/\/feedproxy.google.com\/~r\/techcrunchIt\/~3\/42ah-J5qWIo\/<\/p>","protected":false},"excerpt":{"rendered":"

Google today announced that Google+ in G Suite, the last remaining remnants of what was once Google\u2019s attempt to rival Facebook and Twitter, will now be called Currents. We don\u2019t <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[19],"tags":[25],"class_list":["post-14739","post","type-post","status-publish","format-standard","hentry","category-enterprise-software","tag-enterprise"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t