• Compete
  • Learn
  • Community
ico-magnifying_glass

    SunShot - PVBid Create Bid Wireframe Challenge

    PRIZES

    1st

    $1,500

    2nd

    $500

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

    POINTS: 687.5

    Register
    Submit
    The challenge is finished.
    Show Deadlines icon-arrow-up

    Challenge Summary

    Welcome to SunShot - PVBid Create Bid Wireframe Challenge! In this challenge we are looking to enhance and improve the user experience for a current app that help users create bids and review bids.

    You are provided with a screenshots on how the client imagines the app workflow will look like but we are looking for your help to improve it.

    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.

    Challenge Format

    This competition will be run as a two-round challenge.

    Round 1

    Submit your wireframe for a Checkpoint feedback:
    0. Navigation.
    1. Landing Page.
    2. Sign Up Page.
    3. Create a Bid Page.
    4. Create a Line Item Template Page.
    Notes.jpg: Any comments about your design for the Client.

    Round 2

    Final wireframe plus any Checkpoint feedback:
    0. Navigation.
    1. Landing Page.
    2. Sign Up Page.
    3. Create a Bid Page.
    4. Create a Line Item Template Page.
    5. Generate a Contract Page.
    6. View my Bids Page.
    Notes.jpg: Any comments about your design for the Client.

    Regarding the Rounds:

    • To be eligible for Round 1 prizes and design feedback, you must submit before the Checkpoint deadline.
    • A day or two after the Checkpoint deadline, the challenge holder will announce Round 1 winners and provide design feedback to those winners in the “Checkpoints” tab above.
    • You must submit to Round 1 to be eligible to compete in Round 2. If your submission fails screening for a small mistake in Round 1, you may still be eligible to submit to Round 2.
    • Every competitor with a passing Round 1 submission can submit to Round 2, even if they didn't win a Checkpoint prize.
    • Learn more here.

    Full Description & Project Guide

    Challenge Details:
    The goal of this challenge is to improve the user experience of the current website.

    We are looking for wireframe (Axure) solutions based on requirements below. We’re also looking to the community to come up with interesting ideas for the workflow - we’re absolutely open to creative solutions!

    At the end of this wireframe challenge, we are looking to have a complete solution for the user experience and flow of the application.

    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 screens mentioned in required new sections below, if any requirement is missing in final submission the client will not take a look at it, so make a checklist for the required screens to make sure you designed all of them.
    - Please show us your proposal as a movie or series of wireframes that communicate the user’s intended interaction with your proposed solution.
    - You MUST use 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.

    Notes:
    - Your solution needs to be a Responsive Design Solution.
    - Your wireframe submission need able to drill down for all page flow.
    - Show your wireframe solution for Desktop view. Use this screen size (1024px width and height as required)
    - Feel free to suggest any tools/function that can bring good User Experience for this Application.
    - Side-swipe functionality is encouraged for smaller screens.

    Supporting Documents:
    - Current App Screenshots (Screenshots.zip), please don’t copy the screenshots as we are looking for major redesign and improvement to what we currently have, you can only copy the content of the screens as they are what we are going to use at the end.

    Wireframe Requirements:
    0. Navigation:
    We need the following in app navigation:
    - Bids:
    -- My Open Bids
    -- Create New Bid
    -- All Bids
    - Reminders:
    -- Calendar
    -- To-Do list
    - Trends & Analytics
    - Administration
    -- System Configuration
    -- Template Management
    -- Price Tracking
    -- Module Management
    - Focus on the priority items and how things should be sized.

    1. Landing Page:
    Please refer to Landing-Page.jpg
    - It should very clearly show what user can do with this application and what the application is all about:
    -- What we do.
    -- Customization.
    -- Clarity.
    - The user should be able to sign up or log in from this page, user will be able to log in also using his google plus account or his linked in account.

    2. Sign Up Page:
    Please refer to Sign-Up.jpg
    - Here the user the user needs to fill his information:
    -- First name.
    -- Last name.
    -- Nickname.
    -- Email.
    -- Confirm Email.
    -- Password.
    -- Confirm Password.
    - User will be able to connect using his google plus or linked in information.

    3. Create a Bid Page:
    Please refer to Create-a-Bid-from-a-Template.jpg
    - User will need to fill following data:
    -- Title.
    -- From Template (user can select a ready template), show us how YOU will capture template selection!
    -- Client Info.
    -- Bid Summary.
    -- Set Inputs.
    -- System Components.
    - Summary.
    - Save button.

    4. Create a Line Item Template Page:
    Please refer to slide Create-a-Line-Item-Template.jpg
    - User will need to fill following data:
    -- Title.
    -- Select tab to fill data (we are only concerned with Work Tab here), Please show us solutions other than tabs if you have any.
    -- Scale controller.
    -- Description.
    -- Inputs.
    -- Notes.
    - Save button.
    - Convert to system component button.

    5. Generate a Contract Page:
    Please refer to Generate-a-Contract.jpg
    - User will need to fill following data:
    -- For Bid.
    -- Contract text editor and Save button for editor.
    -- Preview; maybe show this in another view.
    - Send to review button.
    - Send to client button.

    6. View my Bids Page:
    Please refer to View-My-Bids.jpg
    - User will have the ability to search for his bids.
    - User will have the ability to filter his list of bids.
    - A list of bids results will be shown to the user.
    - More results button, maybe pagination here might work better.
    - New search button.

    Learn Axure:
    New to Axure? Here are some quick tutorials to help you get started.
    http://www.axure.com/learn

    Target Users:
    - PVBid users. Typically Sales Minded and Engineering minded people.  Construction contractors.  People with a basic understanding of web navigation.  Not people who are computer savvy.

    Judging Criteria:
    - Efficient - Top 3 priority - The responsive design will demonstrate an efficient use of space to maximize the functionality.  The user has access to all the features indicated in the wireframes and forums while minimizing the click-through and backtracking.  Data changes and entry should bring the user to the next input or to the next launching point.
    - Intuitive - Top 3 priority - All symbols, menus, and the general organizational structure has a natural and easily recognizable path  - The structure is organized, clear and flows from step to step naturally and intuitively. The "standard" next action should be located in the same place and have the same look and feel to it but alternative actions should also be very clear - that is intuitive for the user.  The goal is for a user to be guided comfortably through the process without prior training.  This means the judging panel should have the same experience prior to reviewing the competitor’s notes.
    - Appealing - Top 3 priority - The interface is appealing to view.  This means minimal clutter, comfortable paths, and clear fonts.  The eyes should be drawn to the important information and distractions should be minimized.  “Exhausting” and “tiring” are words to describe what we want to avoid.   Simple and clear symbols should be used.  The number of levels required to edit data should be minimized.
    - Flexible - The responsive design should handle increased dataset sizes as well as it handles the minimum dataset.  The flexibility to handle increased data should maintain the simplicity goals outlined in criteria #3 also.
    - Low bandwidth - The winning design will handle slow internet connections effectively and minimize the bandwidth required to operate the website. Please minimize non-standard graphics.

    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
    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.

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

    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.

    Reliability Rating and Bonus

    For challenges that have a reliability bonus, the bonus depends on the reliability rating at the moment of registration for that project. A participant with no previous projects is considered to have no reliability rating, and therefore gets no bonus. Reliability bonus does not apply to Digital Run winnings. Since reliability rating is based on the past 15 projects, it can only have 15 discrete values.
    Read more.

    ELIGIBLE EVENTS:

    2015 topcoder 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. Create a JPG preview file.

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

    Fonts:

    All fonts within your design must be declared when you submit. DO NOT include any font files in your submission or source files. Read about the font policy here.

    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 here.

    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