BONUS: 5‌ CHECKPOINTS AWARDED WORTH ‌$100‌ EACH

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to the Angelos Download Manager Wireframe Challenge.  In this challenge, we are looking for wireframe (Axure) solutions based off of the provided storyboard, and the requirements from our client.

Round 1

Submit your updated screens for Checkpoint feedback
- Include a basic layout showing how these features fit on the pages in the application
- Show us a version of the Report Download Manager and basic workflow so we can see how you’re approaching the challenge.  
- The main workflow for:
1- Report Detail Screen
2- Report Scheduling Screen
3- Report Download Manager Screen
- Any screens showing interactions and user click-paths
- Notes.jpg: Any comments about your design for the Client

Round 2

Your Final designs for all the required screens with all checkpoint feedback implemented
- Include a basic layout showing how these features fit on the pages in the application
- The fully worked out version of the Report Download Manager - include simulated versions of aspects of the workflow outside of the application, such as email reports and other steps in the process
- This will include all numbered items below: 
1- Report Details screen
2- Scheduled Report Download screen
3- Download Manager screen
4- Notifications and email
- Any screens showing interactions and user click-paths
- Notes.jpg: Any comments about your design for the Client


Challenge Details:
Users have a need to export Excel or CSV files from within the web application.  This challenge will enhance the user experience to allow requested downloads to be managed within a Download Manager, (similar to a Browser download manager, but only use this as a reference) and also add the capability to schedule report downloads for a given date/time, similar to a Calendar invite. As downloads will be queued on the server, a notification system will be used to let users know when downloads are available.

Wireframes Requirements:
Report Download Manager:
The purpose of this wireframe challenge is to accomplish the following:
- Provide a means for users to initiate a Report Download within the Reporting section of the portal.
- Provide a means for users to schedule a Report Download within the Reporting section of the portal
- Allow users to manage their Downloads within a Download Manager screen

1.  Report Detail Screen:
Current system behavior:
- A user clicks on the Report Download button and the server generates the download in realtime for the user and initiates a standard browser file download behavior.
Desired system behavior:
- A user clicks on the Report Download button and the server inserts a report request into a queue which is processed by a back-end server process.
- When the report download request is available for the user to download, the user will be notified by the system notification mechanism. See Notifications below.
Additional functionality:
- The Report Detail Screen should also be modified to provide a link or Button to the Download Manager (see below), and a new Button to allow Report Scheduling (see below).

2. Report Scheduling screen: New screen!
- When a user clicks on the Scheduling button on the Report Detail screen, they will be provided with a new panel or popover.
- This is similar to Calendar applications where the user can schedule the Report to be generated at a particular time, on a particular day, with a Repeating pattern. For example: Every Monday at 8am, or every Monday, Weds, Fri at 8am, or First Monday of each month etc.
- The user should have the ability to name the scheduled report, example ‘Monthly Asset Report’.
- Users should have the option of choosing a XLS or CSV file format.

3. Report Download Manager screen:  New screen!
- Reports generated either by a user clicking on the Report Download button on the Report Details screen, or as a result of a scheduled report download, will appear in the Report Download Manager.
- Consider how to differentiate ad-hoc queued report requests from Scheduled reports within the Download manager.
- Consider how the reports should be displayed, either by icon, card based, or list based and in chronological order but be distinct enough in both location and styling so it’s obvious what they are in relation to
the other items.
- This should naturally allow for sorting, search and management of downloads if there are many reports. 
- Users should be able to click on a report in the Download Manager and initiate a browser download to their computer.
- For scheduled reports, users should have the ability to Edit the Report schedule via the Report Scheduling Screen (2. Above) including the ability to Delete the schedule.
- Users should also be able to Delete a queued Report or Delete a Scheduled Report.
- Come up with a design to show scheduled reports that have not yet been generated, to allow them to be edited.

4.  Notifications.
- The user will receive notifications via email when the file is ready or if errors occur, but also will receive a notification through the portal’s notification system, which is a global element of the application (see Notifications example.pdf)
- The Notification will contain a link that the user will be able to click on to download the ready report
- Notifications should also persist in the portal across browser sessions, so that when a user logs into the portal he will have a visual indicator of the number of unread or new notifications available to him/her. This visual indicator will also update automatically during a browser session in the portal as necessary.

Wireframe Expectations:
- Produce HTML click through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The website must be very easy to use and intuitive. Keep that in mind when designing your solution.
- You MUST cover all use cases mentioned in challenge details below.
- You MUST use the wireframes note pane in every single page you design to explain what items are addressed in that page from the documentation, what things you added/changed/removed, use it to make your idea clearer and help the client to give you constructive feedback.

IMPORTANT:
- We are providing you with the current design serve as the example application framework.  Don’t worry about building out the entire application - just the basic layout such as the pages shown, modules, navigations, icons and links into which the above screens and functionality fit
- The provided screenshots are very wide, but please wireframe towards a standard resolution for a web application such as 1024x768 or 1366x768
- We need the Wireframes to simulate the described functionality for the features we’re improving, so links should link, menus should have options, items that would be populated by databases can be simulated with made-up information

Challenge Resources:
- For this challenge we are providing some screenshots as design guidance for you (screenshots.zip). These are used as reference so you can see where the described features fit into their application and pages, but only focus on the outlined features at this time.

Design Requirements:
- While we are focusing on individual features within the web application, it needs to be created with the context of a Responsive Design
- We are open to suggestions and ideas, so while there are many common design approaches to these solutions, we’re looking for the most useful ideas and implementations

Target Users:
- Inventory control managers.
- Finance managers.
- Logistics managers.

Judging Criteria:
- How well your wireframes provide a consistent user flow and clear information architecture for the application
- Cleanliness, creativity and a smooth and intuitive user experience
- Completeness and accuracy of the areas of functionality

Submission & Source Files:
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

Submission File
Generated HTML files with all the requested contest requirements stated above.

Source Files
All original source files of the submitted design. Files should be created in Axure RP

Final Fixes
As part of the final fixes phase you may be asked to modify your wireframes (content, clickpaths or UI elements) or modify overall layout to best meet the client's needs and for an optimal UX

Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.

Stock Photography

Stock photography is not allowed in this challenge. All submitted elements must be designed solely by you. See this page for more details.

How To Submit

  • New to Studio? ‌Learn how to compete here
  • Upload your submission in three parts (Learn more here). Your design should be finalized and should contain only a single design concept (do not include multiple designs in a single submission).
  • If your submission wins, your source files must be correct and “Final Fixes” (if applicable) must be completed before payment can be released.
  • You may submit as many times as you'd like during the submission phase, but only the number of files listed above in the Submission Limit that you rank the highest will be considered. You can change the order of your submissions at any time during the submission phase. If you make revisions to your design, please delete submissions you are replacing.

Winner Selection

Submissions are viewable to the client as they are entered into the challenge. Winners are selected by the client and are chosen solely at the client's discretion.

ELIGIBLE EVENTS:

2014 TopCoder(R) Open

Challenge links

Screening Scorecard

Submission format

Your Design Files:

  1. Look for instructions in this challenge regarding what files to provide.
  2. Place your submission files into a "Submission.zip" file.
  3. Place all of your source files into a "Source.zip" file.
  4. Declare your fonts, stock photos, and icons in a "Declaration.txt" file.
  5. Create a JPG preview file.
  6. Place the 4 files you just created into a single zip file. This will be what you upload.

Trouble formatting your submission or want to learn more? ‌Read the FAQ.

Fonts, Stock Photos, and Icons:

All fonts, stock photos, and icons within your design must be declared when you submit. DO NOT include any 3rd party files in your submission or source files. Read about the policy.

Screening:

All submissions are screened for eligibility before the challenge holder picks winners. Don't let your hard work go to waste. Learn more about how to  pass screening.

Challenge links

Questions? ‌Ask in the Challenge Discussion Forums.

Source files

  • HTML
  • RP file created with Axure

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30043017