Skip to content

How it works

Emiel Mols edited this page Aug 12, 2015 · 1 revision

How it works

A Happening plugin consists of a zipped code/resource bundle, that is uploaded to the Happening Platform. Code can either be Javascript or Coffeescript.

Client-side code and resources

Client-side code in the bundle is used to render the interfaces and execute logic within the Happening iOS App, Android App or on the web. Once a plugin bundle is uploaded to the Happening Platform, all client-side code and resources will be distributed and run on the devices of participants of happenings with the plugin enabled.

APIs are available to fetch contextual data about the current happening and its members, draw user interface elements and access a synchronized data store.

Server-side code

Server-side code in the bundle is run on the Happening servers. It can define RPC endpoints to be called by client-side code and APIs are available to read/write the synchronized data store, send out push notifications and to send or receive HTTP requests.

See also

Basic topics

API reference

  • API Reference
    • Client
      • [client plugin](client plugin)
      • [client dom](client dom)
      • [client obs](client obs)
      • [client db](client db)
      • [client server](client server)
      • [client page](client page)
      • [client ui](client ui)
      • [client form](client form)
      • [client icon](client icon)
      • [client modal](client modal)
      • [client photo](client photo)
      • [client photoview](client photoview)
      • [client time](client time)
      • [client share](client share)
      • [client map](client map)
      • [client geoloc](client geoloc)
    • Server
      • [server event](server event)
      • [server plugin](server plugin)
      • [server http](server http)
      • [server db](server db)
      • [server photo](server photo)
      • [server time](server time)
  • Example UI elements

Advanced topics

Clone this wiki locally