Transitioning Google URL Shortener to Firebase Dynamic Links
developers.googleblog.com
Transitioning Google URL Shortener to Firebase Dynamic Links
1–10 of 59 posts
Re: Transitioning Google URL Shortener to Firebase Dynamic Links
#2[deleted]
Re: Transitioning Google URL Shortener to Firebase Dynamic Links
#3Since they will be continuing to honor existing redirects, do they gain anything by disallowing new redirects? If it is engineering effort they want to save, they can just stop developing new features, right?
Re: Transitioning Google URL Shortener to Firebase Dynamic Links
#4Total guess here: In addition to having two products that do the same thing, I'm guessing they may want to distance themselves from goo.gl links since a shortened URL with that domain somehow seems associated with Google and seems more legit (as opposed to, say, a bit.ly or ow.ly link.)
Re: Transitioning Google URL Shortener to Firebase Dynamic Links
#5I wonder why Google is reusing the Firebase brand so much? It doesn't really fit with messaging (GCM -> FCM) or links, among other functions. Seems like an odd choice, even if the backend infrastructure/team is the same.
Reminds me of Microsoft reusing "Surface", or prepending "Live" to everything once upon a time...
Re: Transitioning Google URL Shortener to Firebase Dynamic Links
#6I'm partial to ShadyURL: http://www.5z8.info/start-trojan_u9a9hm_aohell.exe
Re: Transitioning Google URL Shortener to Firebase Dynamic Links
#7Total guess here: In addition to having two products that do the same thing, I'm guessing they may want to distance themselves from goo.gl links since a shortened URL with that domain somehow seems associated with Google and seems more legit (as opposed to, say, a bit.ly or ow.ly link.)
Interesting guess. Google does have a URL shortener for google "official" URLs under the g.co domain. And the goo.gl does get used for certain attacks sometimes.
examples of g.co urls: http://g.co/payhelp http://g.co/recover http://g.co/allo
Re: Transitioning Google URL Shortener to Firebase Dynamic Links
#8Since they will be continuing to honor existing redirects, do they gain anything by disallowing new redirects? If it is engineering effort they want to save, they can just stop developing new features, right?
Continuing to honor existing redirects is a relatively simple gesture of goodwill -- it's absolutely what customers expect, it's good for the web, and doesn't need a lot of ongoing effort.
Rather, it looks like they're driving people to a different product intended for a different set of usecases [1]. They want to get out of the generic, commodity web URL shortener business, and drive more of their customers towards more purposeful destination forwarding.
[1] https://firebase.google.com/docs/dynamic-links/use-cases/
Re: Transitioning Google URL Shortener to Firebase Dynamic Links
#9I wonder why Google is reusing the Firebase brand so much? It doesn't really fit with messaging (GCM -> FCM) or links, among other functions. Seems like an odd choice, even if the backend infrastructure/team is the same. Reminds me of Microsoft reusing "Surface", or prepending "Live" to everything once upon a time...
This is to woo developers from both platforms especially iOS devs.
A Google branding is closely associated with Android.
Re: Transitioning Google URL Shortener to Firebase Dynamic Links
#10Total guess here: In addition to having two products that do the same thing, I'm guessing they may want to distance themselves from goo.gl links since a shortened URL with that domain somehow seems associated with Google and seems more legit (as opposed to, say, a bit.ly or ow.ly link.)
This is highly unlikely to be true, considering Firebase Dynamic Links also generates URLs where the domain ends in 'goo.gl' [1].
[1] https://firebase.google.com/docs/dynamic-links/create-manual...