Day Two

11:47 PM Update UX and Polish Work

• DONE - Polish maybe: New main panel UI has Repository Login and Screenname fields;
• DONE - Changed the order history of the added items / user inventory view;
• DONE - When Repository or Username fields are changed the app allows restart/enable button works;
• DONE - Incorporated feedback from Felipe - the Save/Push notes button needs to singnal when new content is pending;
• DONE - Added color feedback to the items that gets into the local user inventory;
• DONE - Andy/UX - The Guide Page is using Google Analytics and some level of app states can be tracked. Not evolved much this yet because of privacy is needed;
• DONE - Andy/UX - The Guide Page is like a wizard so it serves for First Run Welcome, Setup and also additional Information about the project;
• OKAY - The Slides of the Preso are going to be a little bit a mix of the demo and the Guide/firstime/help page
• Have a place to collect feedback; Maybe under the same page;
• Polish the Aggregated view, hide the hide overlay option;
• Contextual Feedback that is sensitive to the Panel area, feedback is sent to through the web site;
• Make the final Wiki page receive a App Stamp concept which is a link back so others can also install and read the page with the Jetpack;

5:07 Update UX loop

• DONE New Welcome page is now remote and is called a GUIDE page;
• DONE Improved Design to Guide page;
• DONE Added Googlel Analytics as a means to measure user activity over Welcome/FirstRun/and other application states. All the states are tracked via access to this a remote external page;
• DONE Changed the Core.js to flip the Guide Page from Welcome to Setup Mode;
• DONE Guide page has a Project section

• Have a place to collect feedback; Maybe under the same page;
• Contextual Feedback that is sensitive to the Panel area, feedback is sent to through the web site;
• Polish maybe: New main panel UI has Repository Login and Screenname fields;
• Polish the Aggregated view, hide the hide overlay option;
• Make the final Wiki page receive a App Stamp concept which is a link back so others can also install and read the page with the Jetpack;
• Document under Project the goal to have a local web server and github mash approach; Check also the operator extension, refer to Prism and Weave as a means to mash data on the backend;
• The Slides of the Preso are going to be a little bit a mix of the demo and the Guide/firstime/help page

Future of Jetpack Session Notes

• Andy/Brian explained how the SDK relates to the current Jetpack prototype, and how the library/signed infra-structure will work on AMO.
• We talked about the need to keep up this work to have our Jetpacks ready when the SDK reaches a condition with UI API in it.
• The 0.2 won't have API
• The 0.4 may have some API in it

Polish Roadmap - 11:43AM status

• Change the Welcome page to be remote and also to offer a rich guide/help place. This will serve as a first time guide and also as a helper location. The following are the group of tabs for this 'Wizard/Guide' content page: Welcome, Setup, Annotate, and Project.
• Put Get Involved, Roadmap, and related materials all under this new Guide page;
• Make this page to be remote so you we can track with analytics;
• Have a place to collect feedback; Maybe under the same page;
• Contextual Feedback that is sensitive to the Panel area, feedback is sent to through the web site;
• Polish maybe: New main panel UI has Repository Login and Screenname fields;
• Polish the Aggregated view, hide the hide overlay option;
• Make the final Wiki page receive a App Stamp concept which is a link back so others can also install and read the page with the Jetpack;
• Document under Project the goal to have a local web server and github mash approach; Check also the operator extension, refer to Prism and Weave as a means to mash data on the backend;
• The Slides of the Preso are going to be a little bit a mix of the demo and the Guide/firstime/help page

Day One

Day Wrap Up

• Documentation: done initial presentation with 4 slides goal
• Feedback: from Brian King to not over explain the wiki repository use
• Source: Checked the SDK experimentation under the project source
• Todo: Add licensing info to the source

Status 3PM, March 10th

• Technical - Added SDK-based experimentation project to the GitHub project repository.

• User Experience, Education - It needs to be more clear that the remote repository is an open-based resource. Maybe the class repository can hold some information that is created by the educator, or by participants, and refers to the framework of annotation, maybe rules, but not to get to a point to limit participants creativity. One example to cover and investigate is licensing. If a given page provides itself as a repository that receives creative commons-based contributions, users needs to be aware of that as they are interactive. To solve that this project proposes that the mediator component can be the cataliser element that provides this information.

Status 2PM, March 10th

• Organizing documentation and presentation goals based on feedback taken from the session where each project provided input to this project.

Status 1PM, March 10th

• Core function frozen;
• Prototype of a local web server is 30% functional and it is aside from the Jetpack due to security limitations in Jetpack ( it does not run XPI )
• Started documenting things related to the SDK, as SDK can be a good way to put a local server and also keep the Jetpack code

Goals

• Better UX for Aggregated View, maybe show a multiple user interaction view
• Better Expanded UI for participant
• Analysis of peer-based Web server

Next steps for the day

• Separated better aggregated view with multiple user activity more clear
• Document the feedback from the other participants