Brivo Labs Venue/Event Check-in iOS App Wireframe Challenge - realworldswift

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

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to the Brivo Labs Venue/Event Check-in iOS App Wireframe Challenge. The goal of this challenge is to come up with a wireframe solution for the new Brivo Labs application that creates and send invites for a particular event. 

In this challenge we are looking for concepts on how this application could work, and what should the user see and experience when using the application. 

This application will be developed under iOS platform on both iPhone and iPad but for this challenge, we are specifically looking for an iPhone solution but keeping in mind the iPad device. 

Round 1

Initial wireframe solution with all the features mentioned in the Requirement section.

Round 2

Final wireframe solution with all the features mentioned in the Requirement section plus any checkpoint updates 


The overall goal of this application is to create a way for the users to create an event and able to select and send invitation on who will attend that event. 

The event may be a meeting, a conference, a conventions, etc... 

Example Scenario: 
Let say John wants to invite Jane to his business for a meeting, so John open this app and started creating the event. He choose the date, time, and person/persons he want to come. Then he send this off and the invitees will receive an email which allows the person to accept or decline the invite. If accepted, it places the event in their iOS calendar. The person could then open up the app and view their status (Active, Pending, Expired) per "company". 

What we are building is actually two apps. One iPhone App and one iPad app. When the specific date/time comes, the user will arrive at the event. They will see an iPad and walk up to it. When the user walks up to the iPad, the iPad app will react when the iPhone gets into a specific range using BLE (Bluetooth Low Energy). A screen will pops up in the iPad app with their information (Name/Email). At that point they press a button that says "check in". The iPad will say something like "Welcome Jane! John has just been contacted of your arrival". This is when John receives a text message.

Please note that you are NOT required to do the iPad app wireframe for this challenge, it was just introduce above to give you background information on the whole process.

User Capabilites

Admin
- Assign SuperUsers (these people will be allowed to send invitations)
- All other features listed below. 

Super User
- Invite users
- All other features below. 

Regular User
- Receive invites


Required Screens

The following are the minimal screen required, you are NOT limited to these screens and we are open in ideas and concepts to support the main idea of the application. 

Login
- user will login using their social identity in Google    

Event Meeting List
- list event status (Active, Pending, and Expired) per company 

Create Event
- user should be able to enter event name, venue/event address
- user should be able to select date, start time, end time, and contacts
- there should be a way to switch between iOS contacts and Google contacts when selecting the contacts
For Reference:
The event invitation that gets sent will be sent using CalDAV (internet standard http://en.wikipedia.org/wiki/CalDAV). Creates an email that allows the user to agree to the invitation and it pop in the user's calendar. 

Invite User
- utilize iOS' calendar and contacts when creating an invitation.
For Reference:
- we will use Event Kit framework to interact with iOS calendars https://developer.apple.com/library/ios/documentation/datamanagement/conceptual/eventkitprogguide/Introduction/Introduction.html
- we will use Address Book framework for iOS contacts https://developer.apple.com/Library/ios/documentation/ContactData/Conceptual/AddressBookProgrammingGuideforiPhone/Introduction.html 

Screen Sizes

- Mobile Standard Size: 320px x 480px

Target Audience

- Business professionals 

Judging Criteria

- User Experience.
- Completeness and accuracy of the wireframe as defined in the spec requirements.
- How well your wireframes provide a consistent user flow.
- Effortless build tablet version based on your mobile version wireframe? 

Submission & Source Files

Preview Image
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it. 

Submission File
Wireframes should be built in HTML or Axure. The resulting files are not critical in this Challenge. The most important point is that all the content is listed and the pages are linked together to show page flow. Keep your source files out from this submission folder.  

Source Files
All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file. 

Final Fixes

As part of the final fixes phase you may be asked to modify content or user click paths. 

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

  • HTML
  • RP file created with Axure

You must include all source files with your submission.

Submission limit

Unlimited

ID: 30045705