Tipboard is straightforward to configure — you define your dashboard's layout with YAML, specify what tiles you want in there (text, pie chart, line chart, bar chart, listing, etc.), give it a unique ID, and that's all you need for a complete dashboard. The only step left is to push your data to Tipboard's tiles, which can be done over an HTTP API.
As of version 1.3.0, you can define multiple dashboards and serve them from a single Tipboard instance by creating one layout config file for each dashboard, and your dashboard will be available at http://your_url.com/ <name_of_layout_config_file>.
Tipboard provides an HTTP API for pushing data in JSON format to the dashboard. This gives you the ability to wire up your data source in any way you like — the only thing you have to do is POST the data to your tile's endpoint.
Tipboard's dashboard layouts are defined in YAML. It follows a grid-based approach where the user defines which tile should go into which column, and which row the column should be in.
You can feed data to widgets directly from a Ruby script/app. Dashing uses job scheduling (rufus-scheduler) to update widgets, and it also provides a command to generate a template for jobs: dashing generate job sample_job. This is convenient if you have an application written in Ruby, or interacts with your data source using Ruby.
Dashing provides an HTTP API for pushing data in JSON format to the dashboard. This gives you the ability to wire up your data source in any way you like — the only thing you have to do is POST the data to your widget's endpoint.
Dashing is no longer maintained by its original creators (Spotify), but it still works as expected. There is an actively maintained fork called Smashing which is identical to Dashing in all aspects.
Dashing is based on Ruby / Sinatra. Its widgets are essentially a collection of Ruby erb templates for layout, SCSS for styling, and CoffeeScript for data polling/interactivity. If you have worked with Rails, Sinatra, or any other Ruby-based web framework and CoffeeScript, customizing widgets shouldn't be hard.
Dashing's dashboard does not work on any version of Internet Explorer, even IE Edge, because it relies on Server-sent Events which IE does not implement.
Smashing's dashboard does not work on any version of Internet Explorer, even IE Edge, because it relies on Server-sent Events which IE does not implement.
Smashing is based on Ruby / Sinatra. Its widgets are essentially a collection of Ruby erb templates for layout, SCSS for styling, and CoffeeScript for data polling/interactivity. If you have worked with Rails, Sinatra, or any other Ruby-based web framework and CoffeeScript, customizing widgets shouldn't be hard.
You can feed data to widgets directly from a Ruby script/app. Smashing uses job scheduling (rufus-scheduler) to update widgets, and it also provides a command to generate a template for jobs: dashing generate job sample_job. This is convenient if you have an application written in Ruby, or interacts with your data source using Ruby.
Smashing provides an HTTP API for pushing data in JSON format to the dashboard. This gives you the ability to wire up your data source in any way you like — the only thing you have to do is POST the data to your widget's endpoint.
Most extensions need to communicate with APIs. Mozaïk eases this by providing a backend, which handles API calls and pushes data to widgets through websockets.
Mozaïk dashboards support multiple devices through adaptive layout. You can either put your dashboard on a big screen in the open space, or consult it on your smartphone.