Show HN: Early-stage Yahoo Pipes spiritual successor

Re:Show HN: Early-stage Yahoo Pipes spiritual successor by fareesh on Tuesday May 30, 2017 @05:36AM (#14444021)

Unrelated to pipes specifically but along the same lines, I feel like app developers ought to conform to a pre-defined standard like schema.org for their respective content so that everything can be inter-operable in theory. That way if I'm using Microsoft Todo or Google Keep or whatever, the potential for Google Assistant or Siri or Cortana to add to whichever Todo App I'm using is already there.

What are the drawbacks behind something like this?

[ Parent | on HN ]

Re:Show HN: Early-stage Yahoo Pipes spiritual successor by comboy on Tuesday May 30, 2017 @05:47AM (#14444062)

No incentive. If your service is used through something else then you are easily replaceable and users don't spend time in your app.

edit: Just to be clear, I'd love that too. Hopefully it will start happening when everything is driven more by micropayments rather than ads. I'd imagine you'll have "gui companies" and "service companies".

[ Parent | on HN ]

Re:Show HN: Early-stage Yahoo Pipes spiritual successor by onli on Tuesday May 30, 2017 @06:14AM (#14444173)

It's also really hard to do. I mean, imagine how one would achieve interoperability for a project like this. Placing blocks via an API from another service? The language/spec supporting that and everything else would be too complex.

But thankfully we have RSS for the data representation, which is a related idea, just the output side. The core of that idea is what enables this site in the first place.

[ Parent | on HN ]

Re:Show HN: Early-stage Yahoo Pipes spiritual successor by bsandert on Tuesday May 30, 2017 @05:46AM (#14444057)

Vendor lock-in.

[ Parent | on HN ]