4 ms·
Turn Google's strengths into weaknesses by opening up all of Yahoo's products (Search, Mail, Finance, Maps, Sports, News) to developers to be maximally programm
by nl 14y ago
Turn Google's strengths into weaknesses by opening up all of Yahoo's products (Search, Mail, Finance, Maps, Sports, News) to developers to be maximally programmable.
This sounds great, in a handwavy way. In practice though I'd like to hear specifics about what Yahoo could/would offer that Google doesn't already?
Search: https://developers.google.com/custom-search/v1/overview https://developers.google.com/custom-search/v1/overview
Mail: https://developers.google.com/google-apps/gmail/ https://developers.google.com/google-apps/gmail/
Maps: Seriously? I'm not even going to bother linking to the Google Maps API
Google doesn't have great developer stories in Finance, Sports or News. I guess there are some opportunities there, but exactly what they are isn't obvious.
Anyway, isn't this whole strategy what Yahoo tried in the 2006-09 timeframe? It failed then (mostly by failing to bring in revenue) - why would it be different now?
- mbell 14y ago> Maps: Seriously? I'm not even going to bother linking to the Google Maps API There is a reason many have transitioned to OSM based data and tile hosting services: price. The Google Maps API is no longer the "no-brainer" that it once was among developers.
- jlarocco 14y agoGoogle charges the most for maps because they have the best service. And generally speaking, I don't think competing on price is a great strategy for turning the company around. The OSM map services will have a big price advantage because all of their data is free, even though it's not as good as Google's. And if Yahoo enhances the data, or gets their own data and tries to charge a premium, then they're back to where they are now trying to compete with Google... I'm not saying they can't make a better service for cheaper, but their focus should be on making a great map service, not on cutting the price.
- Evbn 14y agoGoogle drastically cut back on the price increase. It isn't so bad anymore.
- ramanujan 14y agoTo clarify, here's my thoughts: 0) Embed apps on the frontend: The APIs you mention are good, but they are backend APIs or APIs for customizing (say) maps within a widget on your site. I'm talking about opening up the frontend too. A prosaic way of thinking about it is an App Store for each large Yahoo subdomain, starting with search.yahoo.com but ultimately allowing very deep apps that pull from many Yahoo properties. Importantly, app installation buttons should be heavily but tastefully promoted: every relevant URL, map result, or email from an app provider should allow a one-click install with ID and billing optionally from Yahoo. 1) Concrete example: suppose Yahoo allowed website proprietors to embed a widget to the right of search results that linked to them. The widget would display if it met the performance and load requirements of Yahoo Search, and not if it didn't. Given that Yahoo is now powered by Bing, this could be a Windows Phone tile sort of thing. Visualize a minified version of what you'd click on the website to see. Facebook could show your last 5 messages, Mint your last few payments, and so on. Basically, take microformats to the next level and allow site proprietors to create their own onebox experiences. 2) Data: In addition to opening up apps, take every piece of data that Google never made open for fear of giving away a proprietary advantage and throw open the doors with an aggressively priced data.yahoo.com API, both to monetize and to differentiate against Google. 3) Re: Yahoo's open stuff in the 2006-2009 timeframe -- that was grassroots and built by engineers, never really pushed by their leadership as the future. 4) The Y Prizes: One other thought is that if this open strategy works, Yahoo could announce an acquisition tournament for each hot new closed web property. All the Facebook, Twitter, Foursquare, Quora, and Pinterest clones would register for a three month competition to build an API to Yahoo's spec, with the winner being acquired for a fixed up front cost of say $10M. Cheap for Yahoo, life changing for the 5 man dev teams that would arise for a shot at this prize. These Y Prizes would allow Yahoo to stay ahead of the curve on new stuff without trying to do everything themselves. 5) Moral high ground: Yahoo as the platform for the Open Web would give them the moral high ground and goodwill to pick (and win) a bunch of fights. Always punch up.
- nl 14y ago0) Embed apps on the frontend: The APIs you mention are good, but they are backend APIs or APIs for customizing (say) maps within a widget on your site. I'm talking about opening up the frontend too. A prosaic way of thinking about it is an App Store for each large Yahoo subdomain, starting with search.yahoo.com but ultimately allowing very deep apps that pull from many Yahoo properties. Importantly, app installation buttons should be heavily but tastefully promoted: every relevant URL, map result, or email from an app provider should allow a one-click install with ID and billing optionally from Yahoo. Read that GMail API again - it is designed to do exactly what you are proposing. The section you need to read is https://developers.google.com/google-apps/gmail/#gadgets https://developers.google.com/google-apps/gmail/#gadgets Both Yahoo & Google tried this previously with OpenSocial. It bombed badly.