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

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to Gmail Archiver Wireframes. The main goal of this contest is to create wireframes for web-based Google application that will allow archiving of mails in Gmail.

Client of this project has internal employees that use Gmail for their email needs.  However, some of these employees have been reaching the 25 GB storage limit imposed by Gmail. So they have decided to create Gmail Archiver application that will allow employees to archive / store their email messages to a cloud-based (online) repository with virtually no storage restrictions. See the contest spec and conceptualization for more details.

Round 1

-Complete all the use-cases under 
1) Generic User Functionality (Common functionalities for all registered users)
2) End User Functionality
3) eDiscovery Analyst User Functionality 
-If you can add more use-cases, it would be great!
-Notes : Any comments about your wireframe, make sure all pages have correct flow!

Round 2

-Complete all the use-cases menitoned below in the spec
-Implement any changes/suggestion given by the client during Milestone.
-Notes : Any comments about your wireframe, make sure all pages have correct flow!


Gmail Archiver application will allow employees to archive / store their email messages to a cloud-based (online) repository with virtually no storage restrictions. Email can be archived by clicking on “More” menu in Gmail. Users will be able to select which emails to archive, and using the Gmail Archiver they will be able to view these emails or restore them, so they’re available in their actual Gmail accounts again.

When user loads Gmail Archiver they will be able to see main dashboard which will include recent activities, archive request history (with statuses), the remaining storage space in their Gmail account, activities the user still needs to complete, and alerts (both broadcast alerts and system alerts). The dashboard will also include options available to the user based on their user role (End-User, Archive Admin and eDiscovery Analyst).

Contest Requirements:
For this contest you will need to complete the use-cases under the following functionalities, 

1) Generic User Functionality (Common functionalities for all registered users)
2) End User Functionality
3) Archive Admin User Functionality
4) eDiscovery Analyst User Functionality

Please read the attached conceptualization document to learn more about the use-cases under each functionalities. 

Target Audience:
-
Internal Employees of client company
-Any other users running Gmail Archiver App

Judging Criteria:
Your submission will be judged on the following criteria:
-Usability and intuitiveness of the interface design.
-Completeness and accuracy of the wireframe as defined in the requirements.
-How well your wireframes provide a consistent user flow
-How well you implement the required data and any suggestions, interactions and user flow you recommend (provide any notes or comments for the client)

Submission and Source Files Requirements
Submission File
All requested contest requirements/screens as clickable HTML files unless otherwise stated in the contest details.

Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.

Preview Image
Create a 1024x1024 JPG or PNG file in RGB color mode and place a screenshot from your submission within it.

Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.

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:

2013 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: 30028775