Skip to main content

Multi-platform application toolkit

Deliverables

Trial-ready CMS core backend

First, working CMS core backend, suitable for use in the large scale trial.

Final Modules/Plug-ins

Based on the feedback from the trials in WP6, two updates will be produced in M16-17 and M 20-21, covering improvements where needed. The resulting code will be delivered as the final deliverable in M21.

Trial-ready CMS core frontend

First, working CMS core frontend, suitable for use in the large scale trial.

Final CMS core frontend

Based on the feedback from the trials in WP6, two updates will be produced in M16-17 and M 20-21, covering improvements where needed. The resulting code will be delivered as the final deliverable in M21.

Trial-ready Modules/Plug-ins

First, working Modules/Plug-ins, suitable for use in the large scale trial.

Final CMS core backend

Based on the feedback from the trials in WP6, two updates will be produced in M16-17 and M 20-21, covering improvements where needed. The resulting code will be delivered as the final deliverable in M21.

Usability findings

This document is an important deliverable for the UI design team. The information gathered to the report includes prioritized usability findings with both poor usability and good usability. Findings of poor usability are grouped e.g. to major and minor findings or even more so to three - five different categories, based on the severity. Report can include user comments and suggestions for corrections in places seen necessary and obvious.

Initial MPAT Scenarios

This deliverable will describe the content creator and consumer perspective scenarios derived in the first phase of Task 2.1 and 2.2

System requirements and existing solutions v2

This deliverable is an update of D4.1. It takes into account findings from the first pilot evaluation.

Final Plan for the Communication of Results

Final plan for the communication of the project results.

Initial Plan for the Dissemination and Exploitation of Results

Initial release of the plan for the dissemination and exploitation of the project results and the associated business model.

UI design

This deliverable affects to the content of usability tests and planning. UI Design is the target of tests and thus the material needs to be in a certain level before testing can start. First test round is done with wireframes with little or no interaction. Later the design will evolve to include more detailed descriptions and interactions. Usability findings help to iterate the UI design and meet the user needs better. UI design document includes UI graphics and style guides which are used in the implementation phase.

Initial Plan for the Communication of Results

Initial release of the plan for the communication of the project results.

Test plan v2

Revision of D3.1, which takes into account findings from the pilot evaluations.

Contributor guidelines

This deliverable describes guidelines for 3rd-party developers who want to develop Plug-ins or Themes or who want to contribute to MPAT core.

Final UI design

Revision of D3.3, which takes into account from D3.5.

Final Plan for the Dissemination and Exploitation of Results

Final plan for the dissemination and exploitation of the project results and the associated business model

Test evaluation

Document containing users’ feedback and measurements acquired from the two pilot phases and the resulting answers to the research questions specified in D6.1

Final Project Summary Report

Final Project Summary Report

Updated MPAT Scenarios

This deliverable will describe the updated scenarios, based on D2.1, but updated with the result of the second phase of Task 2.1 and 2.2

Usability findings v2

Revision of D3.2, which takes into account findings from the pilot evaluations.

Developer tools and development guidelines

This deliverable describes guidelies for developers within the MPAT project. Guidelines include: code style rules, guidelines for commenting code and use of developer tools for versioning, build and testing.

Pilot execution report

This deliverable will describe the preparation and execution of the pilot trials.

System requirements

This deliverable documents findings of the requirements and state-of-the-art analysis conducted in T4.1.

Test plan

The test plan covers information about test procedure, methods that will be used, and participant descriptions (e.g. age distribution, occupation, sex). Document will also have test tasks the participants are performing on the test sessions, and material for the moderator so that she can conduct each session the same way. Additional material can cover for example templates the test observers can use to mark down their findings during the test sessions.

System architecture and API documentation

This deliverable documents findings from T4.2. It will provide the following information: system architecture describing interfaces of individual components of the MPAT Core, the information flow between the components of MPAT Core and documentations of the API for Plug-in and Theme developers.

1st Project Periodic, innovation and standardisation report

1st Project Periodic, innovation and standardisation report

System architecture and API v2

This deliverable is an update of D4.2. It takes into account findings from the first pilot evaluation.

Test setup specification backend

This deliverable will describe the technical specification for the pilot trial phase (channels used for trial, AIT description, bandwidth capacity used, broadcasters’ backend configuration, management/storage in CMS of information gathered by the app).

Product license

The open source license that will be adopted for the product which will be released at the end of the project.

Research questions and measurement methodology

This deliverable will describe the questions for the trials and the appropriate methodology for evaluating them, as determined in task 6.1. It will reflect an intermediate status of the pilot preparation work of task 6.1. It will focus on the research questions, the means and methodology to gather qualitative and quantitative feedback with regards to the first pilot phase.

Project website

The setup of a project website to be used for internal and external communication

Searching for OpenAIRE data...

Publications

Interactive storytelling on HbbTV. Linear, yet interactive: Paper presented at TVX 2017 adjunct. Adjunct publication of the 2017 ACM International Conference on Interactive Experiences for TV and Online Video, June 14-16, 2017, Hilversum, The Netherlands

Author(s): Fuhrhop, Christian; Zwicklbauer, Miggi; Patz, Nicolas; Broadbent, Matthew; Steglich, Stephan
Published in: TVX 2017 Proceedings, Issue 2, 2017

Multi-Platform Application Toolkit (MPAT)

Author(s): Miggi Zwicklbauer
Published in: 27. Fachtagung der FKTG, 2016

Interactive Storytelling & Audio Apps for HbbTV

Author(s): Nicolas Patz (Rundfunk Berlin Brandenburg)
Published in: Forum Medientechnik und All Around Audio Symposium, 2016

Multi-Platform Application Toolkit

Author(s): Miggi Zwicklbauer, Matthew Broadbent, Jean-Claude Dufourd, Christian Fuhrhop, Stefano Miccoli, Fabian Schiller, Ville Tuominen
Published in: ACM TVX 2016 Adjunct Proceedings, 2016