From 296067f613e2f0bc576652e9ee66bd9aea20b4c6 Mon Sep 17 00:00:00 2001 From: August Lilleaas Date: Tue, 29 Oct 2013 17:06:20 +0100 Subject: [PATCH] Mentioning intents, see issue #18 --- concept/applications.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/concept/applications.md b/concept/applications.md index 911f0b4..75d3ccc 100644 --- a/concept/applications.md +++ b/concept/applications.md @@ -38,4 +38,10 @@ All apps run completely sandboxed and communicates over a simple JSON api with t ## App Store -It should be decentralized as well, so there could be an "app server" app for GDC to host your own app repository. A user could then subscribe to that server using its URL and could browse, buy and download apps directly from there. \ No newline at end of file +It should be decentralized as well, so there could be an "app server" app for GDC to host your own app repository. A user could then subscribe to that server using its URL and could browse, buy and download apps directly from there. + +## Intents + +There should be an Android-like intent system where any application can provide e.g. "calendar", "file-sync", "addressbook" and so on. The intent has a protocol that must be implemented which is specific to the various intents. 3rd party intents can also be provided, perhaps through some kind of central register over intents and their purposes. + +This is much more flexible than having a calendar app build in to the system itself. It's more flexible for the developers since we don't have to rely on a specific implementation of a calendar. And it's more flexible for the user, they can chose their own calendar app, instead of being forced to use the one that's built-in.