Thanks, I wasn’t aware of that feature (and I pay for Enterprise gsuite, so that tells you something about either my attention to Google product details, or the level of advertisement of this feature :)
I do wonder if this is actually building a semantic knowledge graph of the content, vs. just providing a dynamic facade/aggregator for other apps’ search APIs, and doing “old style” text indexing/searching within Workspace services. It looks like the former based on a cursory read of the docs.
It would be more challenging to build a knowledge graph over {drive,slack,Jira,…} documents, but if they just build a knowledge graph within Workspace that could provide more reason to use Docs vs. Notion/Confluence, or Google Chat over Slack. So there is actually a strong product/market reason to build this as a native feature even if you can’t solve it for other apps.
I do wonder if this is actually building a semantic knowledge graph of the content, vs. just providing a dynamic facade/aggregator for other apps’ search APIs, and doing “old style” text indexing/searching within Workspace services. It looks like the former based on a cursory read of the docs.
It would be more challenging to build a knowledge graph over {drive,slack,Jira,…} documents, but if they just build a knowledge graph within Workspace that could provide more reason to use Docs vs. Notion/Confluence, or Google Chat over Slack. So there is actually a strong product/market reason to build this as a native feature even if you can’t solve it for other apps.