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

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to Big Blue Notice Something Do Something Wireframe Challenge! "Notice Something... Do Something" is basically IBM's equivalent of the popular IFTTT (If This Then That) service. Think of "Notice Something... Do Something" as a simple assistant that spends it's time watching for something specific to happen and when it does, takes an action on your behalf. The combination of an event to watch for and an action to take is called a recipe. You can create your own or use recipes that others have shared.

It will most likely tie into RSS feeds from internal IBM applications, such as Connections, and output emails, Connections posts, and send notifications.

Round 1

Submit your wireframe for a Checkpoint feedback:
1. Navigation
2. Browse Recipes
3. Create Recipes
4. Edit/Remove Recipes
Notes.jpg: Any comments about your design for the Client.

Round 2

Final wireframe plus any Checkpoint feedback:
1. Navigation
2. Browse Recipes
3. Create Recipes
4. Edit/Remove Recipes
Notes.jpg: Any comments about your design for the Client.


Challenge Details:
The goal of this challenge is design this “Notice Something…Do Something” mobile application, it will be equivalent of IFTTT but for internal IBM data. IFTTT lets you define events that you want detected, and actions to be executed when those events occur -- so basically tying together two Web services that wouldn't typically work together. The application will be delivered via iOS 8.

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

Recipe Examples:
- Those are just examples of possible recipes so you can understand what a recipe mean.
1- Send yourself an email anytime your manager updates their blog.
2- Get a notification on your mobile device every time your approval is requested.
3- Automatically add to my calendar any vacation days I define in the Vacation Planner application.
4- Post to a team support blog every time an outage to one of your servers has been detected.
5- Automatically check-in to a check-in service (such as the IBM Employee Check-in and Broadcast service) every time you arrive at the office.

Channel Examples:
Here are some sample IBM applications that you could use as channels for your wireframes:

* IBM Connections Blog -- user would need to specify the blog name, and whether you want to know about new blog entries or new comments
* Media Library -- the user would need to specify the media library topic to watch
* Vacation planner -- the user would need to specify whose vacation to watch for
* email, phone notifications, Connections status -- that's an output channel

Screen Size:
- Mobile Resolution: Design for iPhone 6 Retina Display 750px x 1334px.

Use Case Scenario:
- David is an IBM employee.
- David logs in to the application using his Intranet ID and password.
- David sees existing recipes.
- David chooses to use a recipe, and he can customizes it for himself.
- David can start from the list of channels to create a new recipe.
- David can edit his existing recipes, or removes one that they are no longer using.
- David can enables/disable recipes.

Required Features:
1. Navigation
- How does the user navigate this application?
- Include navigation that you think fits with this application
- Focus on the priority items and how things should be sized

2. Browse Recipes
- User will be able to browse existing "recipes".
- User can also choose to use a recipe that he finds, and customize it.

3. Create Recipes
- User can create new recipes.
- When recipe is made, gives choice to make public, private or to share recipe to social media.

4. Edit/Remove Recipes
- User will be able to edit/remove recipes.
- Make a recipe as private or public; public only shows the recipe “formula”, not personal information.
- User can also enable/disable recipes.

Target Users:
- IBM Employees.

Judging Criteria:
- How well you translate the requirements into an attractive and usable design.
- Cleanliness of your graphics and design.
- Design and User Experience.

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.

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:

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

  • RP file created with Axure

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30047589