Why Marissa Mayer should acquire IFTTT and go all in on Yahoo Pipes

Holy cow with the grandiosity of the title I would expect a master 5 year plan about how Pipes will take over the world. Instead it's just another 'aggregate my aggregators non-problem' that will be relevant to a fraction of a fraction of nerds. Of course as soon as the value prop for the piped companies becomes lower than the value prop for Yahoo they will simply turn them off. But that's not to worry, because the value prop for the piped content will ALWAYS be higher than for Yahoo. How exactly does one go "all in" on schlepping around other people's content? Yahoo was in fact just that, to begin with...

The blog post doesn't make a compelling business case beyond "it'd be cool". If Yahoo! were to buy IFTTT for the purpose of consolidating their mobile experience (and I'm not even sure what that is supposed to entail), what's to stop Twitter, Facebook and all that from turning their feeds into the service off? Twitter have already pulled that kind of stunt.<p>Currently, IFTTT is a fun toy for hackers and power users who want to do slightly off-the-wall mashups. If it got bought up and became a more critical part of the infrastructure of a big company like Yahoo!, you can bet there'd be some intervarsity tech company politics going on.

This post does not deliver what it promises in the title. It gives no reason why Marissa Mayer should acquire IFTTT. It's not particularly insightful either.<p>I'm trying to guess why it has 53 votes. The only explanation I can come up with is that there must be a number of IFTTT fans who upvoted it just because it praises IFTTT. That would mean there is a high likelihood that this comment would be downvoted.

I know 3 startups trying to solve aggregation of metrics for analytics.<p>I worked for a management consulting company and produced such a system based on aggregating data from across a global corporate network and producing dashboards in SharePoint.<p>Yahoo could have an enormous impact on KPIs, dashboards and metrics for consumers and business were they to want to. And with it, one hell of a revenue stream.<p>IFTTT could solve data/metric aggregation for consumers, marketeers and other less technical users.<p>And if an export from IFTTT could produce a Yahoo Pipe, then a developer (or slightly more skilled user - a good Excel user perhaps) could then make it do even more.<p>It could be used to read from Excel. From CSV. From SharePoint. From databases. From web pages on the internet and intranet. Everything.<p>Aggregate news headlines concerning your company. Create cohort charts with data from different and unconnected systems. Combine data from servers to mailing list campaigns to observe impact much quicker and to identify fully which campaigns work best. Or just grab the numbers from many systems to find out which system is showing the wrong value.<p>So much is possible that companies struggle with today because their data is siloed in disconnected systems... or some of it is external and they have no interface to it.<p>Glue between Twitter and App.net? That's just trivial. A real prize will be to aggregate anything and everything and allow it to be processed before reporting on it.<p>It's not glamorous... but I can say from experience that the company I worked for successfully sold the product I made for £50k licenses to large companies. The demand is there.

If something like Feedburner, (which was several orders of magnitude more popular than Pipes and IFTTT combined) is forced to shutter, I don't think a tiny service for power users is going to turn around a publicly traded company as large as Yahoo. Call me crazy.

&#62; Will Twitter deprecate support for RSS to lock down our tweets? Will Facebook block IFTTT to control how we share our filtered photos?<p>I wouldn't be the least bit surprised if they did. Doubling down on Pipes with Twitter heading in the direction it is right now would be a really stupid move.

So Yahoo should buy IFTTT to help people migrate from Twitter to App.net?<p>There are probably some good products to be built on integrated social experiences (or internet glue), but Pipes+IFTTT doesn't sound like an actual end-user product.

OP doesn't realize that big companies like Yahoo cannot sign API contracts; they get terminated immediately. Remember Ping/Facebook?<p>I think the ToS termination issue is the single largest risk facing start-ups operating in another company's ecosystem. How can Yahoo buy you if your API key is deactivated as soon as the deal closes?<p>I love IFTTT, but I think their long-term prospects are bleak. Urban Airship had the same problem.

If the market opportunity here is defragmentation of social networking, then Yahoo should acquire Buffer[1], and get themselves a dead simple product that "just works." IFTTT and Yahoo Pipes are awesome for technically savvy folks, but it's a non-solution for the vast majority of the market.<p>[1] <a href="http://bufferapp.com" rel="nofollow">http://bufferapp.com</a>

This is hardly a convincing article for justifying why Yahoo! acquiring IFTTT is a good idea. I get IFTTT is a great service, but it's nothing particularly special, there's even a Rails clone of it on Github that Yahoo! could modify and use to start their own IFTTT like service.<p>I am however an avid Pipes user and fan. It's definitely one of the strongest tools Yahoo! have in its arsenal with exception for Yahoo! BOSS which I am currently using for my new startup which relies on search engine data instead of scraping it myself.<p>It was a nice try. I don't understand how this reached such a high spot on the homepage.

IFTTT and Yahoo Pipes are completely different products with different business models. The customer excitement around IFTTT is great to see, but IFTTT is still figuring out their business model, and they need to finish development of their new platform and SDK. Once they get these things rolling I can see them being an attractive acquisition target. But even then, I don't see Yahoo Pipes and IFTTT co-existing nicely, and I'm not sure that Yahoo would make sense as an acquirer.

I've no idea about the finances of it all, but in terms of usage, the two services are a natural fit. IFTTT has easy integration with lots of services, but Yahoo! Pipes has a lot more flexibility in terms of functions and logic.<p>That said, I'd like to see some sort of hosted version or library to do this. Yes, you can do a lot of this yourself, but if the plumbing (hrrr) already existed, you'd be free to focus on the actual logic instead of the infrastructure.

That homepage design has to be the most distracting blog theme setting ever.

Yes, average user wants to do visual programming.

I kinda feel sorry for Marissa Mayer, the internet collective has put a lot on her.<p>I can see why, many great and well loved services have faced death by yahoo over the years. Clearly people do still care about the future of yahoo (or at least the services they consume) otherwise we wouldn't keep seeing these kind of posts.<p>I just hope that there is a plan, and it would do much for me if MM made some sort of statement to the effect that Yahoo will properly support acquisitions rather than let them slowly die.

If the Pipes/YQL team that is still at Yahoo had any interest in duplicating the functionality of IFTTT or Zapier, they could just do it.

I think about this a lot. Not just for my personal accounts but then add in the pages and micro-brands one has to manage if you have a small business, or a band, or just a blog you have an identity for. It becomes a juggling mess.<p>Ha, lets have an master service that manages user-created services on these platforms. Then let Twitter play wack-a-mole with that...

A question I've always had about posts like this in general: What would happen if Mayer actually did this? Would she not bet met with derision for apparently guiding the company with advice gleaned from a blog post? Do "Company X should do Y" articles actually hurt their own chances of being fulfilled?

Nice article, however Yahoo! could probably figure out a way to ruin the awesome UX IFTTT currently has. And with the track record Yahoo! has, I would hope they wouldn't buy it. <i>Yahoo! is where good apps go to die. Haha</i>

I miss the point. Of course if this setup becomes common they will block it as well. They don't want you to do that. If you find a loophole they will fix that.

There is also <a href="http://tarpipe.com" rel="nofollow">http://tarpipe.com</a> which is similar to ifttt but with a gui more like yahoo pipes.

What if IFTTT acquire Yahoo! ? Now or then Yahoo! is going down and down. No one depend on Yahoo!. We just use it as secondary platform.

my problem with ifttt: it does it's job just fine, so well I don't remember the last time I logged into ifttt.