Challenge Overview
Project Overview
Our partner is developing a state-of-the-art tablet based sales and order processing tool. Their sales team will be managing client visits, tasks, calendars, notifications, and order processing all through this tool. The platform is the Apple iPad. Want to learn Swift? Great - why not get paid for it, we need your help! There will be a long series of challenges over the coming weeks leading to the final product, so get involved now!
Setup
In order to obtain the code source to modify for this challenge, you will need to be added to the UNI-Mobile github repository. Make a request for access in the forums.
This contest will not require you to do any direct work with the Salesforce Mobile SDK, but it is a required element of the overall application. As such you will need to be able to login to Salesforce the first time you run the application in order to access the other components of the application. The credentials are as follows:
-
Username
-
Password
-
newuser@123
-
Again, you will not be required to utilize the Salesforce Mobile SDK for any of the customization you are doing in this challenge. But the application leverages it, so logging in is essential.
This contest will require you to hook into the AccountViewController’s Fit Session checklist item button. To get to the Account screen, you will need to log into Salesforce with the provided credentials. This will take you to the Homepage, which has a Calendar. There should be a Meeting (EventsTableViewCell) in that calendar. When you tap on that it will expand, and tapping the Person Icon will take you to the Account Screen.
Contest Requirements
For this contest you will be tasked with building a new modal module for the UNI-Mobile application. For this module you will create the base set-up screen, for what will be a larger module in future challenges. The path to view this module will be as such: from the seller homepage view an account, then tap the “Fit Session” button in the left sidebar.
This module is composed of 3 screens - The Fit Session home screen, the Create/Edit Department screen, and the “Show Tips” overlay.
Detailed Requirements
Detailed requirements will be provided in the challenge forums.
General Guidelines
The Data Model objects referenced in this challenge should all be created in the Model subproject within the UNI Repository. If you have any questions, please ask in the forums, we will help you determine if additional objects not pre-built may be necessary.
“?” icons will trigger tooltips (style defined previously) with two sentences of lorem ipsum (to be edited later).
For this challenge if you would like to pull in third party form generation frameworks, that is allowable in order to satisfy any requirements asking for ease of configuration or reusability. If you do incorporate 3rd party frameworks for the construction of these forms, please ensure that these frameworks are Open Source software, and are available with an MIT or similar distribution License. Code submissions that use 3rd party frameworks will be judged based on the ease of use and extensibility of those frameworks.
Environment Setup
GIT: The project will use a code repository at Github, please see additional details and participant responsibilities under Submission Guidelines.
Xcode: All code development should be done in Xcode 6.1 and tested in the simulator.
Framework: Code should be developed with the Cocoa Touch framework using Swift and must compile against iOS SDK 8.0 with a deployment target of iOS 7.0.
Get Started
- Request access to the project in the challenge forums
- Fork this project: git@github.com:cloudspokes/UNI-mobile.git
- Checkout this branch: https://github.com/cloudspokes/UNI-mobile/tree/fit-session-setup-ui
- Write and submit your code as a zip file
Final Submission Guidelines
Submission Guidelines
Submission Guidelines
- Cocoa Touch framework Xcode 6.1 project with well commented code
- Code must compile against iOS SDK 8.0 with a deployment target of iOS 7.0
- Upload all source projects as a zip
- After submission phase has completed, make a pull request targeting this branch
- Provide documentation of any special configuration required to run your code.
GIT Guidelines and Requirements
All code for this project will be maintained at Github. Challenge participants will have to request read-only access to the repository during the challenge and are expected to fork and do their coding on the challenge branch. Once contest submission closes, the project owner will update the code in the challenge branch to reflect the current state of development. The winner of the challenge will then be required to update their fork to the current state of the development repository and will be responsible for handling merge conflicts when updating their fork. They will then create a pull request.