...but what if we could surface part of the app itself...
What is it with the repeated usage of 'surface' here, instead of the more obvious and common word 'show'? Is it something to do with Android API naming, or something else?
Only a slight exaggeration, based on my observation of specimens in the wild (many years at Google).
...or you're not "moving the needle."
I've been in agency for a decade or so, and yeah, this is pretty much how it works. Don't even get into the use of the word "agile" around here.
"Surface [verb]: To make easily readable or noticeable on a web page or app If you'd rather avoid it: Highlight; showcase; present; display"
"It’s easy to see how handy this word is for web developers, page designers, and business strategists, because it efficiently conveys both the goal and the act of making something appear online in a more prominent way. Although its meaning is transparent, it’s still new and specialized vocabulary, and probably will sound odd to most people."
That is, "surface" means the data is brought to you in your current context, whereas "view" means you are taking to a new context that includes the data.
In this discussion, they are saying that when you search for "lyft" in on-device google search, it will incorporate Lyft info into the search results, as opposed to giving you an option to launch the Lyft app.
So when they say "we will surface this data" they mean we will show it, not that we will allow the normal software to show it like normal.
* "bundle" (as in "app bundles", a feature that lets Google Play deliver an installer with a stripped down set of resources to the end user's device)
* "action" (as in the new feature of the UI known as an "action" which some have alternatively describe as a "visible intent" or a "deep link with parameters." or something)
https://developer.android.com/reference/android/app/slice/Sl...