-
Notifications
You must be signed in to change notification settings - Fork 5
Appnet
Head to an [Urbini readme] (https://github.com/urbien/urbini/blob/master/README.md) for the Appnet rationale.
There are several ways for apps to communicate today. There is IFTTT, and Zapier, and there is mashups. How is Urbini different?
-
Urbini is open. Anyone can write an Urbini adapter to any existing Web API. Check out those we wrote already. Once an Urbini JS adapter to app's WebAPI is created, any app (with the permission from the user) can access other app's data in a uniform way [as Backbonejs models].
-
Urbini is not limited to point-to-point app communications. Zapier [describes itself as Unix pipes] (https://zapier.com/developer/). Urbini is not pipes, it is a graph. Why does it matter? Because now you can write an app that draws data from many other apps as if it was one database. Wait, no ifs, it is one database, on user's machine.
-
Appnet Urbini is client-centric. Unlike IFTTT and Zapier, and like most mashups, inter-app communications in Urbini happen on the client. Unlike mashups Urbini unifies all communications around a local, client-side database.
-
Appnet automation. The coolest thing about data-centric vs api-centric comms is that now automation becomes possible. That means Urbini provides UI generation for all the data, allows to define triggers and other types of inter-app scripts, supports push notifications on data changes, etc.
-
Urbini is open source. But you already know that, silly.