It's the typical situation: no user uses more than 5% of Excel's functionality -- but users don't use the same 5%.
Where G Suite is great is 3rd party integrations, especially ones targeting small/mid size companies.
It's the typical situation: no user uses more than 5% of Excel's functionality -- but users don't use the same 5%.
Where G Suite is great is 3rd party integrations, especially ones targeting small/mid size companies.
O365 took the idea and ran. Yes, their web-based UI isn't as rich, but it has some decent collaboration, really good mobile apps and of course excellent desktop native apps.
Google could have held their lead IMHO if they kept building out their Docs/Sheets to be closer to feature-parity with Word/Excel and started earlier on good mobile and desktop native apps (which don't even exist!)
I love me some google docs for collaborative editing, but your right in the scaling of large docs in Word and Excel functionality.
I'm also amazed at how much suckage people are willing to put up with in O365, but still consider it a better choice than Google Docs for the company.
Sharepoint is complete crap, and the off Sharepoint file syncer client is absurdly flaky, but there is a huge tolerance for that kind of thing.
Or at least, it's not the biggest factor when considering making year+ commitments to one office suite or another.
Price, familiarity and feature-richness are definitely in MS favor.
That said, just as Skype and Skype for Business are very different beasts under the hood, One Drive and One Drive for Business are also quite different, the latter being shoehorned on top of SharePoint.
AFAIK, it's all basically OneDrive under the hood now. Which is great because all the Groove/SharePoint based syncing was awful before.
Which brings up another O365 nit, MS has these direct consumer services and O365 services all on different account silos such that when I log into O365 I have to go through a decision tree that answers two levels of questions about which _account_ my company email address is referring to: MS Personal vs Organization Issued vs Organization but Personally Created (not sure how the last category exists)
Outlook for Android is the biggest piece of shit to hit mobile and O365 on the web takes a huge smelly dump on linux users. I am still angry at my employer for foisting this garbage upon us, just so the nontechnical exec team can have their precious Outlook
Lync has been renamed to Skype For Business, and is very similar in terms of user experience to the standard Skype app.
> "I still cannot figure out where our documents are stored... is it on the windows share? OneDrive? SharePoint? My personal Dropbox??"
You can hardly blame Microsoft for the slack IT policies at your workplace.
What a colossal marketing cockup
https://support.office.com/en-gb/article/Let-users-add-exter...
"Don't blame Microsoft for slack IT policies" What? Like hell I'm not blaming them. It's not my fault they offer a bunch of shitty, complicated, barely-working, overlapping, should-be-simple services that nontechnicals can barely wrap their mind around. It's not my fault my employer hired me to work on Linux code and then has a sudden Windows come-to-Jesus moment. (I'm sure theres some stupid sales rep to thank for that...) It's not my fault that Microsoft can't write decent AJAX!
If they would simply follow standards we wouldn't have this problem. But then of course Micro$oft wouldn't make as much ca$h, and we certainly cant have that now can we....
So Microsoft tell the employees at your company which places to store their documents do they? Why does your company not standardise on how documents are stored?
>"It's not my fault that Microsoft can't write decent AJAX"
Examples?
"Lagging" is an interesting choice of words...
Re-encoding MP4s to a slight variant of MP4 so that my demos are visible to Win7 installs. Because they flip out. Known issue, I'm told, but not fixable. Win7 is frozen!
You may not like Win10, but I think Win7 is a ghastly experience that is about as fun as bamboo shoots under one's nails (for developers). It has 0 affordances for modern software development EXCEPT misapplications of the Windows UI. Oh, also before I forget: old Win7 font rendering is substantially uglier than new Win10 font rendering! Critical stuff!
If "just works for email" is your criterion, it's a mistake not to use Chromebooks in the first place.
Do you mean something like Tableau/QlikView/Pentaho/PowerBI?
OWA works just fine on Chrome on Linux, I use it every day.
Sharepoint sucks, but then again the whole wiki/CMS/whatever category of things that Sharepoint is a representative of is almost without exception a huge festering cesspool of villainy and suck.
You're saying that all the other options are worse??
(As for OWA, I regularly encounter full-page reloads for simple actions, am frequently logged out after my first click on anything, and it is almost obnoxiously slow for the speed of internet that we have. And this is Office365... previous versions of OWA were pretty good though)
Sharepoint is the server, Exchange is the server. The Sharepoint server hosts Web OneDrive like the Exchange server hosts OWA Outlook Web Access. If you want to use the desktop client for either, instead of the browser javascript, you can download and install the binary.
With SharePoint I can share documents and directories with other people in my company.
As much as I think SharePoint is "mediocre", Google Doc is just shit when it comes to sharing[1].
[1] The only sharing google doc does well is sending a link to ONE SINGLE DOCUMENT to a bunch of people by EMAIL ONLY.
Everything there is accessible, visible and searchable (modulo access permissions). It's de-facto shared.
---
With a Google Drive, all contents is private, only visible by you, only accessible by yourself.
Other people can't access your stuff, people can't search your stuff, people can't even know what may or may not exist.
If you want to share something, you have to email a link a single specific document of yours to selected people (who will each individually have to accept the invite).
How do you keep track of what is shared? by who? to who? how do you share stuff to groups/teams/businessunit? Basically, google docs intuitively goes against everything you want to do in an entreprisey context.
Yes. That's one of the thing they miss really bad for sharing. It should have been there for 10 years already.
However, IMO comparing SharePoint to Google Drive is apples and oranges (and really OneDrive consumer is the appropriate comparison) SharePoint uses metadata and a content type model to organize everything, which is indexed so it can be searched on and have custom filters, views, and forms built off of it. It's a double edged sword though in that as much as it helps organize lots of documents, it also has a lot of maintenance overhead (and a lot of special nuances that people need to learn). It also supports a lot of features that are aimed at implementing simple business processes like workflows, versioning, and document templates.
More recent updates have been trying to gloss over a lot of the complexity and simplify the UI, to make it look more like a consumer level product I guess.
https://blogs.office.com/2016/09/26/sharepoint-online-sync-p...
the new onedrive client with selective sync is nice if you have something like say a 400mb autocad drawing youd rather not stream everytime you double click it. you can sync just the files in the group/documentlibrary you want.
Compete with Microsoft and forever spend your time with bug fixes, parity issues, and new features the other guy implements.
... OR create enough of the part that essentially means productivity app, but then branch out into your own space and create a product that differentiates itself and creates lock-in.
Google knows that doing the latter is like a dog forever chasing fox and never winning, so it eventually called timoeut on parity and branched off into doing something new and exciting.
Virtually no one uses Google Docs or Sheets. Instead, they struggle on without it, or have their department purchase an incredibly expensive version of Office.
The Google experiment has failed in our organisation. Google Groups and Gmail is a bit of a disaster. Google can't even do basic things, like relabel all email older than a certain date. And the admin interface is ridiculously slow, and frankly buggy. One time, I logged into this frequently used interface and discovered that I got prompted with a post it note every freaking time. That might not seem like much, but it slowed me down and we are under the pump at the moment.
Overall, Google has such great ideas but is totally let down by an utter lack of polish and a total inability to improve their UX, and ensure that they finish off features and products.
So much potential let down by incredibly simple UX errors. It's unbelievably disappointing :(
Did they ever have it? Did they ever care about it? Google Docs languished for such a long time and Google never made a real push into the Enterprise.
But I haven't noticed any improvements to google docs since the early days. You can't create templates, you can't upload fonts, a million other things that make it not really usable in a professional setting for external communication.
No, Google was never going to own the market segment once MS got into it seriously. Google could only mark time until that event.
1. We were still paying a subscription for Office while on G Suite, the cost to change to fully O365 was at worst net-neutral, but definitely saved about $5/mo per head on paper.
2. Calendaring for Google sucks. We're a distributed team, we have recurring meetings, and lots of updates across various devices. Meeting updates were frequently not persisting to users, cancelled recurring meetings were not going away, etc. Heaven forbid you have someone that wants to cling to Outlook as their mail client, because then you'll have a whole host of other issues.
Outlook/Exchange may be 'non-standard' as far as not playing by the specs, but it really is the standard for anyone who's spent time in a big company, and it was getting really embarrassing when our Google Calendar invites were not playing well with our potential and current clients' Exchange systems and Outlook clients.
I do miss the Google Apps sign in to all the various services we use. Some have integration w/ O365 or generic identity authentications, but most either don't or charge a lot extra. Other than that, I don't miss a single thing from G suite that O365 doesn't do just the same or a little better.
Here is the root of your problem - your organization was in Exchange ecosystem before switching to G Suite. We use Google Calendar throughout (I worked at Google) and never had problems.
The final straw really was the problems we were having with everyone else's Exchange systems. If I'm organizing a meeting from Google and you're a client of mine on Exchange, there is a high likelihood that if I have to update the meeting details or change times you will not be seeing the correct information on some or all of your devices.
If we didn't have to interface with other companies, sure- we could live with it. But if I'm paying the exact same money or less to get a service that doesn't have these problems, why shouldn't I switch? It's not like I'm supporting the 'little guy' by choosing GOOG over MSFT.
That is not his problem. That is google's problem. Ironically, thinking that this is the user's problem may be the root of google lagging in this area.
Microsoft Exchange is deeply entrenched in the corporate world. When you send an invite to a client (or vice versa) and it fails due to integration issues, the typical client will be thinking "oh this is weird; I don't have issues with accepting or sending invites to anyone else!". You don't want to be that guy in your client's head.
* You can't export a list of meeting attendees into any other format (like CSV or Excel) with their response status without additional tools or Gscripts
* If there's more than 200 people on an invite, you don't get RSVPs
* There's no reliable way to update all meetings in a recurring series - some things you can change, others you're stuck flicking through your calendar and updating each one individually
* The weird lack of support for any rich-text in the body of a meeting - except if you first write it up in GDocs, then copy and paste it. Then it works fine.
* It allows you to update the time of a meeting but not send updates to the attendees. Why would I ever want to do that?
In my experience G Suite and O365 are equivalent. Useful for a few things, rubbish for anything serious.
https://products.office.com/en-us/business/compare-more-offi...
so that would be $3/4 of a million a year to jump to include all desktop apps.
Although I think the newer generations care a bit less about e.g Word etc and they are also more tech savy on doing hard things on google sheets etc, while the older generations might find it extremely hard to convert from Excel to google sheets etc.
Although another factor is laws etc and privacy policies. Google is much less flexible than office365 when it comes to who owns the data, although of course you have to pay for office365 while for google stuff usually you dont have to pay hence your companies docs might be owned by google and I don't see any sane human being wanting that.
GSuite is $10/user and offers similar products, but you have to pretty much support yourself.
The $20 extra a month I pay for my small team is negligible.
The company I work for pays even less per person than I do, with the enterprise licensing and the MS cash that gets thrown at us for integrating with them. Our first year of 365 is basically free, same with our switch from our data center to the cloud.
We are looking to save millions a month by making this move.
Since use mostly linux - desktop version of Office365 is useless for me.
To sum it up: one third Office price - no functionality lose for me and some functions not available in Office at all.
At this point, it's a marginal cost vs. benefit game: the cost differences between the two services are virtually 0 (and if not, getting closer each month), and the benefits show that we have more to _lose_ than gain from the switch.