News for hackers. Stuff that matters.

ycapplication

Re:Ask HN: Why can't we just build one app that does it all? on Thursday January 05, 2017 @10:58PM (#13333804)
I don't think it's extreme and I think many people favor such a system on a categorical basis.

How do you know when all creative value has been unveiled and it's time for convergence? I would argue that the very nature of creativity makes this perhaps impossible to answer and best attempts to do so in the categories that you mentioned would be at best local maxima.

If I'm understanding the main issue you've raised, it's that utility would be higher from the productivity gains under a single agreed upon platform than exists today due to productivity limitations from fragmentation. There may be an equilibrium point, and I'm not convinced the market isn't fairly decent at finding it. Look at how difficult it's been for other vendors to enter the smartphone market and how quickly developers were willing to abandon Blackberry to decrease their development costs. I wouldn't be surprised if economic forces favor unification and that many hope for ecosystem diversity at the cost of lost utility/productivity for long term benefit. Thiel certainly argues the former in his recent book.

Re:Ask HN: Why can't we just build one app that does it all? on Thursday January 05, 2017 @10:03PM (#13333580)
It appears to me that your critique may be of capitalism/free enterprise which extends far beyond the scope of apps. It's quite a big topic to unfold, but in the example you provided, stagnation and a lack of convergence on what constitutes the ideal app are low hanging fruit to be addressed.

Note that in some industries the benefits of shared utility clearly outweigh those of competition, the classic example being infrastructure.

Relevant xkcd: https://xkcd.com/927/

We love Zapier and I'm really excited to start playing around with this. One concern I've always had as an engineer using Zapier was how it accounted for unique trigger events.

1. Concerning privacy, for API's that don't offer webhooks for instance, does Zapier poll the API and then store some of our data in order to confirm that new records are indeed new? 2. Concerning robustness, what insurance is there against any failure that the zap will catch up with its triggers?

We don't currently use Zapier for anything mission critical and I'm hesitant to recommend it, but it would be pretty cool if we could use it for making zaps that contain more sensitive data and are more critical.

The privacy policy states: "Your user-facing Task History is stored for the life of your account so that you can monitor Zapier activity and replay failures." [1] I was hoping for a bit more of a technical explanation, though, and could only find pricing FAQ's.

[1] https://zapier.com/help/data-privacy/