Challenge Overview
Welcome to the Agon AngularJS App Improvements Challenge. This is a First 2 Finish challenge where the first acceptable submission wins the challenge and closes it.
We are looking for a submission in the next 12 hours. Thus, we request you to ask questions early and submit your solution that meets all the requirements as soon as possible. A valid submission in the next 12 hours (beginning from registration start and ending in the next 12 hours or when the challenge closes - whichever is earlier) will get a $200 bonus (up to 3 submissions).
Project Overview
The customer has an analytics tool that provides a filter focused UI and visualizations that map funding processes. The solution is a Windows desktop application that is being converted to become more web-based in a separate stream of work.
We are currently building a web front-end for our analytics tool. In the final version it should have dashboard-like behavior, as it should be able to place multiple visualizations of the same dataset on a single screen.
Besides these visualizations an important part of our analytic tool is the 'tv remote' to navigate through the data. To filter data we use structured natural language queries (called filter). By stacking multiple of these queries, users can filter the data, on which visualizations are created. The client is also looking to include a visual programming editor that allows users to visually define/configure (template) sentences that specify refinements and metrics.
Challenge Details
This challenge is really simple. We will provide you with the existing application and you need to make the following changes to it:
AngularJS App Improvements
-
The existing application uses an old UI Prototype. Replace this completely with the provided new UI Prototype. All features should continue to work. (A little background - Originally there was a functional prototype that included the sentence builder piece. Then there was a UI Prototype that did the styles. They had to be merged, basically the old code had to be skinned. The prototype is what it should look like, the js project is how it should function.)
-
Use technically correct names for the pages in the provided UI Prototype. The names should convey the purpose of the page clearly and you should not use generic names. Except for any third party libraries, any files specific to the application should be named correctly. This is only for the templates.
-
We would like you to validate that the data types of the Schema are adhered to when a new document is created / updated. The application should raise an error if the wrong payload is passed to it.
Consolidating Navigation
-
The current angularjs application in the UI Prototype should be restructured to be a Single Page Application (SPA) and make it use partials (ng-view / ui-view directive).
-
The navigation between partials should continue to behave as it does currently in the prototype.
- Whenever navigating between two pages / partials, if there are any open popups or windows, then they need to be closed before beginning the navigation.
Final Submission Guidelines
Submit the application with all the above mentioned requirements taken care of. You can submit this through the Submit and Review tool for this challenge.