Description: The user can choose a specific representative to contact

• set up the representative dropdown menu
• configure the representative variable in the contact screen
• use the representative's email address

Description: Prevent the user from voting more than three times a day with a pop-up message

• set up a tally for the amount of times a user has voted in that day
• set up a time to refresh the user votes (every morning at 12 am?)
• if it is past the next time the user can vote, then the vote count refreshed
• if it is not past the next time the user can vote, then an alert message is sent to the user
• if possible, set the vote buttons to hidden if the user's vote count has been exceeded
• if possible, show a vote countdown on screen and configure autolayout

Description: Each Bill has a title label, the scope (Senate, House of Reps, etc.), and an area for votes

• add the fields of title, scope, different vote fields, status, etc. to the TableViewCell
• connect the fields to the BillCell class
• configure BillCell to update all the fields with a given Bill
• set up autolayout so the bills display properly
• set up the bills' votes array

Description: The user can click on any profile to view the detailed view

• connect the segue of a user profile picture to their detailed view
• set up segue identifiers and use them in the segue method
• send the necessary information (i.e. the User object) to the ProfileViewController
• if the user profile is not the user that is logged in, then disable the edit button for the description

Description: Questions fill the screen with a TableView

• create the QuestionViewController and link it to a view controller
• embed Navigation Controller and connect
• create necessary text fields and title and table view and link to view controller
• set up TableViewDelegate and TableViewDataSource with viewDidLoad calls and create necessary methods
• create a QuestionCell class and connect it to a TableViewCell in the view controller
• add a question label to the TableViewCell and connect to QuestionCell class
• call the questions from Parse in the QuestionViewController and set them to a questions array
• Use the Question model to set a Question to the QuestionCell
• configure autolayout in Storyboard just for TableView and set TableViewCell to ensure questions display

Description: The user can log in to an account with their email/phone number and password

• set up view controllers with navigation and tab bar controllers according to spec
• create the LoginViewController and link it to a view controller
• create necessary text fields and title and link to view controller
• check user's account by sending information to Parse
• send an alert if the user tries to register with empty text fields
• send an alert based off the error from Parse
• configure autolayout in Storyboard
• setup persistence for user in SceneDelegate

Description: The user's profile is linked to relevant Representatives (they can also choose Representatives)

• obtain zipcode of current user from Parse
• get representatives from ProPublica API
• if possible, use zipcode to configure relevant representatives using the representative information. if not possible, set default representatives to representatives from your zipcode
• ensure Parse is configured to accept a modification to the representative array, and send the change to the User object

Description: The user can create an account with their email, username, first name, and password

• create the RegistrationViewController and link it to a view controller
• create necessary text fields and title and link to view controller
• create user's account and send information to Parse
• send an alert if the user tries to register with empty text fields
• configure autolayout in Storyboard

Description: The question the user votes for, if the vote count changes to be higher than the above question, moves up on the screen without the user refreshing

• figure out how to sort the array of questions based on voteCount (or sort the array of incoming questions from Parse based on voteCount)
• display the questions in the correct order
• if possible, highlight the top three questions
• if possible, have the question move up the screen (animate) without the user refreshing

Description: Add additional fields for the user to write into to contact their representatives

• add the user's email and last name as a field and connect it to the view controller
• display the first name of the user on the contact screen
• configure autolayout

Description: The user can swipe down on the screen to refresh

• set up a RefreshControl and configure it to the Parse call
• when a question is posted, it appears at the bottom of the question count

Description: The user can click on the profile tab to view a detailed version of their profile

• add the description, party, and interest fields
• connect the fields to the view controller
• use the User object to obtain the correct values and update the fields
• setup autolayout, and learn how to setup for views larger than the screen

Description: Can GET and POST to Parse Database for all necessary calls

• create a Heroku app
• setup Parse dashboard
• create User model that subclasses from PF
• create Question model that subclasses from PF
• create Bill model that subclasses from PF
• run a test call to Parse

Description: Bills fill the screen with a TableView

• create the BillViewController and link it to a view controller
• embed Navigation Controller and connect
• create necessary text fields and title and table view and link to view controller
• set up TableViewDelegate and TableViewDataSource with viewDidLoad calls and create necessary methods
• create a BillCell class and connect it to a TableViewCell in the view controller
• add a bill title label to the TableViewCell and connect to BillCell class
• call the bills from Parse in the QuestionViewController and set them to a bills array
• Use the Bill model to send a Bill to the BillCell
• configure autolayout in Storyboard just for TableView and set TableViewCell to ensure bills display

1. Following methods seem not in the category of UIViewController methods. Can we define a better pragma mark?
   

   Represent/Represent/View Controllers/BillsViewController.m

   Line 38 in 4b010de

   - (void)fetchBills: (BOOL)getNewBills {

   
   

   Represent/Represent/View Controllers/BillsViewController.m

   Line 59 in 4b010de

   - (void)updateBills {

   
   

   Represent/Represent/View Controllers/BillsViewController.m

   Line 64 in 4b010de

   - (void)getBillsParse: (BOOL)getNewBills {

   
   

   Represent/Represent/View Controllers/BillsViewController.m

   Line 92 in 4b010de

   - (void)initRefreshControl {

2. The naming of bool getNewBills is not clear to me what it means. Can we name it better?
   

   Represent/Represent/View Controllers/BillsViewController.m

   Line 38 in 4b010de

   - (void)fetchBills: (BOOL)getNewBills {

3. It looks like you are fetching/mutating information through Parse in a "View" class. This violates Model-View-Controller pattern. What can we do to set a clean boundary between View and Model?
   

   Represent/Represent/Views/QuestionCell.m

   Line 55 in 4b010de

   [self.question.author.profilePhoto getDataInBackgroundWithBlock:^(NSData * _Nullable data, NSError * _Nullable error) {

   
   

   Represent/Represent/Views/QuestionCell.m

   Line 108 in 4b010de

   [self.question saveInBackgroundWithBlock:^(BOOL succeeded, NSError * _Nullable error) {

4. The code pointers in (3) may cause another issue that there are multiple network roundtrips on one load. This is not performant. Can we reduce the network roundtrip and fetch all information at once?

5. Please add documentation to all public properties and methods in the header file. e.g.

   Represent/Represent/Models/Bill.h

   Lines 20 to 39 in 4b010de

   	@property (nonatomic, strong) NSString *billID;
   	@property (nonatomic, strong) NSString *number;
   	@property (nonatomic, strong) NSString *type;
   	@property (nonatomic, strong) User *sponsor;
   	@property (nonatomic, strong) NSString *title;
   	@property (nonatomic, strong) NSString *shortSummary;
   	@property (nonatomic, strong) NSString *longSummary;
   	@property (nonatomic, strong) NSDate *date;
   	@property (nonatomic, strong) NSString *question;
   	@property (nonatomic, strong) NSString *result;
   	@property (nonatomic) NSInteger votesFor;
   	@property (nonatomic) NSInteger votesAgainst;
   	@property (nonatomic) NSInteger votesAbstain;
   	@property (nonatomic, assign) BOOL *headBill;
   	@property (nonatomic, strong) NSString *committee;
   	@property (nonatomic, strong) NSString *forDescription;
   	@property (nonatomic, strong) NSString *againstDescription;
   	+ (Bill *) updateBills: (NSDictionary *)dictionary;
   	+ (NSDate *)formatDate:(NSString *)dateString :(NSString *)timeString;

Description: Each Bill displays votes of representatives and total vote count

• add fields for the names of each of the representatives
• set up representative votes based on the top representatives or the representatives the user is following
• display the representative votes through the BillCell class
• add colors to the UI
• set up autolayout so the bills and votes display properly

Description: add an external library for visual polish

• add the cocoapod for moving the keyboard for textfields
• find an external library for visual polish that you want to use
• download cocoapod and integrate
• test functionality and enjoy the pretty view!
• if time/necessary, improve UI and add animations!

Description: The user can click on the profile tab to view their profile

• set up the ProfileViewController and attach it to a view controller
• set up and embed Navigation Controllers
• add and setup a UIScrollView
• add the username field and the profile photo field, and connect them to the view controller
• call Parse to obtain the User class
• create a new User object
• initialize the profile's basic view
• setup autolayout if the UIScrollView is not showing up correctly

Description: connect to ProPublica API using API Key and run network calls

• create an APIManager class
• add API Key and configure call
• test a call for bills

1. Move Utils.h and Utils.mm to a folder instead of at the top level.
2. Please add detailed comment to explain the code in following method:
   

   Represent/Represent/View Controllers/BillsViewController.m

   Line 87 in d761c67

   dispatch_semaphore_t semaphoreGroup = dispatch_semaphore_create(0);

   
   

   Represent/Represent/View Controllers/BillsViewController.m

   Line 259 in d761c67

   dispatch_semaphore_t semaphoreGroup = dispatch_semaphore_create(0);

3. Avoid multiple empty lines in code:
   

   Represent/Represent/View Controllers/LoginViewController.m

   Line 137 in d761c67
   
   

   Represent/Represent/View Controllers/LoginViewController.m

   Lines 142 to 144 in d761c67
   
   

   Represent/Represent/View Controllers/PostQuestionsViewController.m

   Line 70 in d761c67
   
   

   Represent/Represent/View Controllers/ProfileViewController.m

   Line 72 in d761c67
4. Following lines are repeated when setting up the view for the 1st-person and 3rd-person profiles. They can be consolidated to a single method.
   

   Represent/Represent/View Controllers/ProfileViewController.m

   Lines 67 to 69 in d761c67

   	self.descriptionField.text = self.user.profileDescription;
   	self.descriptionField.textColor = UIColor.blackColor;
   	self.descriptionField.font = [UIFont systemFontOfSize:17 weight:UIFontWeightRegular];

5. Thanks for adding method documentation. I'd suggest to add doc for the input params and return value. e.g.
   https://google.github.io/styleguide/objcguide.html#example
   

   Represent/Represent/Models/Question.h

   Line 37 in d761c67

   /*Is used externally to create a Question with the given arguments.*/

6. Nice to see consts at the top of the file.
   

   Represent/Represent/Utils.mm

   Line 11 in d761c67

   static const NSArray *passed = [NSArray arrayWithObjects: @"Passed", @"Agreed to", @"Amendment Agreed to", @"Nomination Confirmed", @"Bill Passed", @"Cloture Motion Agreed to", @"Motion Agreed to", @"Motion to Proceed Agreed to", @"Motion to Table Agreed to", @"Cloture on the Motion to Proceed Agreed to", nil];

Description: The user can refresh any profile

• set up a RefreshControl and configure it to the Parse call
• when a new description is posted, it appears with refreshing
• configure scrolling for as much information as possible in the description cell

Description: The user can submit a question

• create a PostQuestionViewController and connect it to a view controller
• add a Navigation Controller
• add text fields and connect them to the view controller
• add buttons to "Cancel" and "Post"
• add action to the cancel button to clear the field and go back to the Questions Screen
• if possible, add the representative drop down menue
• create a method in Question class that posts a Question
• call the method from the Question class when the "Post" button is pushed
• ensure the call to Parse executes correctly
• if the question field is blank, set up an alert

Description: The question the user posts appears on the screen without refreshing

• ensure the question the user posts is added to the correct questions array
• if refreshed, the question appears at the bottom of all questions
• the question appears at the bottom of the screen without refreshing
• if possible, the question is highlighted when posted and the user is taken there

Description: enable search and filtering on bills

• use the search query from the API
• create Bill objects for the search results but no duplicates
• display the results with the correct votes as well
• add a dropdown filter menu
• configure different filters to show different results (search by house vs. senate)
• make sure the configurations are also applied when the user searches

Description: The user can swipe down on the screen to refresh the bills

• set up a RefreshControl and configure it to the Parse call
• when a new bill is posted, it appears with refreshing
• configure unlimited scrolling for as many bills as exist

Description: The user can click on their description field to edit it

• add a button next to the description field and connect it to the view controller
• configure the button action to let the user edit the field
• update the user's description with the new description on screen
• update the user's description with the new description on Parse
• if possible, configure the button so it only displays when the user hovers over the description label
• setup autolayout with the button

Description: At the top of their profile, the user can choose to directly contact their Representatives

• create a ContactViewController and attach it to a view controller
• add necessary navigation controllers
• send the User information through the segue
• set up a small prompt and text field and connect that to the view controller
• update the variable of the small prompt with the message that the user types

Description: The user can send the message using their email

• ensure the user's email is accessible
• add a send button and add the action to the contact screen
• either use an SDK or something else to configure the email to be sent through the user's email, or open up the native email client with the pre-formatted message
• configure autolayout

Description: The user can toggle between Representatives and their questions

• set up the top representative section to be a dropdown menu
• display the representatives from the followedRepresentatives array in the dropdown menu
• configure autolayout for the dropdown menu
• ensure the questions are properly filtered by representative
• change the representative based on the representative that the user chooses
• add a MBProgressHUD to display while Parse is re-filtering

Description: a required part of the app is to add an SDK

• look at other SDK's for different functionalities if you don't want Facebook's
• add an SDK

Description: Each Question has a vote button, the question, and is linked to a representative

• add the fields of username, timestamp, votes, question (and a button to vote) to the TableViewCell
• connect the fields to the QuestionCell class
• configure QuestionCell to update all the fields with a given Question
• set up autolayout so the questions display properly
• set the representative label at the top of the page to be the user's first representative
• filter the questions to be only from that specific representative

Description: The user can vote on a question

• connect the vote button to the QuestionCell and add its action
• update the Question voteCount and update labels
• send data back to Parse