• ProfileSetupFragment = screen to set up all REQUIRED user information before can start buddying! PIN #, profile picture, and Trusted Contacts

• EditTrustedContactsFragment = separate screen linked from ProfileSetupFragment for the user to set up multiple Trusted contacts.

• **Note: Lots of sample code is already written on similar Fragments to display how the interface, StartActivity, and fragments work together, it should help you get started! Also, a ton of this is much more intricate to implement than the other issues, so don't feel pressured to finish everything if you don't have the time for it!

• Following the wireframes on README, create layout.xml files and implement Fragments for: "Profile Setup Screen" and "Edit Trusted Contacts Screen"

  • ProfileSetupFragment{ }:

    • invoked by either LoginFragment - when user registered AND logged in, but not yet setup profile
    • or by RegisterTwoFragment - when user just registered official account in Parse database
    • Expect to receive the User object we are creating! (B/c we are still building the profile of a to-be-created and not logged in user)
      • Resource: How to pass data between Activities and Fragments
    • create instance of SAFragmentsListener{ }
      • e.g. private SAFragmentsListener SAListener;
    • attach this instance to StartActivity (which implements SAFragmentsListener)
      • e.g. SAListener = (SAFragmentsListener) context;
    • on "Take a Photo" button:
      • Intent to Camera (just like in last Instagram project)
    • on "Upload from Gallery" button:
      • Intent to get file from Photo Gallery
        • Resource: How to use Intent to get a pic from Android's camera gallery
    • Next to the "Set Trusted Contacts" button (as shown in wireframes):
      • display status: "not done" in red when user not yet have 1 Trusted contact
      • display status "completed" in green, when user has at least 1 Trusted contact
    • on click "Set Trusted Contacts" button:
      • call SAListener.toEditTrustedContacts(User object);
    • on clicked (1) on menu (3 horizontal lines) icon in top navigation bar and clicked (2) "Log out" button:
      • call SAListener.toLoginFragment();
      • Purpose: Allows user to log out without setting up a profile! Profile setup will be enforced in LoginFragment by another issue.
    • On "Complete Profile" button AND if profile pic, PIN, and trusted contacts != null:
      • set user's profileSetUp = true;
      • Check if there is a current user logged in:
        • e.g. if(ParseUser.getCurrentUser() == null)
        • Log the user in! (e.g. when just created account from RegisterTwoFragment)
          • otherwise --> the user was logged in by LoginActivity and just needed to finish setting up the profile
      • Intent to MainActivity
    
    

  • EditTrustedContactsFragment{ }:

    • invoked by either ProfileSetupFragment or SettingsFragment
    • Expect to receive the User object we are creating! (B/c we may still building the profile of a to-be-created and not logged in user)
      • Resource: How to pass data between Activities and Fragments
    • Creates a TrustedContact object and uses TrustedContact's setter method to POST request with the Parse database! (must wait for Parse and java models to be done by another issue)
      • Each TrustedContact is inputted into the User's trustedContact's list!
    • create instance of SAFragmentsListener and connect to StartActivity in the same way{ }
      • e.g. private SAFragmentsListener SAListener;
      • SAListener = (SAFragmentsListener) context;
    • Max of 5 Trusted Contacts
    • RecyclerView and Adapter used (to display a Trusted Contact in a format on every row):
      • Every RecyclerView row/Adapter .xml displays Trusted Contact’s:
        • First name
        • last name
        • Relationship to user
        • mobile phone number
        • email
      • Displays the current Trusted Contacts if any
        • On long click (or whatever you prefer to edit a row):
          • Opens Dialog box to edit the current contact or delete it entirely
          • NOTE: Dialog Box is essentially a little pop up form or message that can take a small number of user inputs and act on it. It shouldn't be extremely hard to implement
            • Resource: Android Dialog Box Guide
      • If user has room to add more (e.g. current # of Trusted Contacts < 5)
        • Display a “+” or “add" button:
          • On click → display a different .xml on that row with empty containers to enter the needed info
      • Otherwise display message that user at the max Trusted Contacts allowed
    • on click back button or on click "save" button (wasn't included on the wireframe!)
      • call SAListener.toProfileSetup(User object);

• For extra help on connections between interfaces, activities, and fragments:

  • You can see the example of how @jmnguyen1999 did her "Snapagram" this way with an in-class interface, under StartActivity.java and the StartActivity packaged Fragments!

• Make login/logout activities
• Write login/logout functions

• Make new project, titled "Wings"

• Setup all activities and layout.xml files needed. Design them according to the wireframes, and just ensure to make a Fragment container!

  • StartActivity{ }:
    • to switch between all not often used Fragments (Login, Register 1 and 2, ProfileSetup, and EditTrustedContacts)
  • MainActivity{ }:
    • to switch between all oftenly used Fragments (Home, UserProfile, SearchUser, ChooseBuddy, OtherProfile)
  • SettingsActivity{ }:
    • an in between, all account settings can be edited here (email, name, uses EditTrustedContacts Fragment)

• Set up all interfaces to be used a listener from Fragments to Activities (How Fragments can invoke a method from the Activity to switch to next Fragment):

  • StartActivityListener{ }: StartActivity and all Fragments that need to be shown on the activity will use this.
    • These methods are ALL IMPLEMENTED IN StartActivity:
    • toLoginFragment(): switches to Login screen
    • toRegisterOneFragment(): swtiches to Register 1 Screen
    • toRegisterTwoFragment(): switches to Register 2 Screen
    • toProfileSetUp(): switches to Profile Setup Screen
    • toEditTrustedContacts(): switches to EditTrustedContacts Screen
    
    
  • MainActivityListener{ }: works in the EXACT same way but with MainActivity and its Fragments
    • toHomeFragment()
    • toUserProfile()
    • toSearchUser()
    • toOtherProfile()
    • toChooseBuddy()
  • @jmnguyen1999 implemented this way for her Instagram copy project, "Snapagram", but with in-class interfaces! If you need to see how it works you can take a look at "SignUpFragment.java" and how it works with "StartingActivity.java"
  • NOTE: Also more in depth on the Google Docs outline!

• Input all color hex-values, text fonts, text sizes, icons, etc that was used in the wireframe into their corresponding res folders so others can easily design their layout files!

• Push to GitHub

• Following the Figma wireframe, create a layout.xml for SearchUserFragment:

  • It looks like the layout format will be:
    • Search bar
    • Title: (e.g. "Friends")
      • RecyclerView w/ GridLayoutManager
    • Title: (e.g. "Others")
      • RecyclerView w/ GridLayoutManager
    • . . . .
    • Resource: Using RecyclerView w/ GridLayoutManager
    • Resource: This is Kotlin but may provide some insight: RecyclerView w/ GridLayoutManager
  • Should be endlessly scrollable, can use the CodePath files used to do this for past projects:
    • EndlessRecyclerViewScrollable: can use for every RecyclerView section

• Implement SearchUserFragment:

  • uses a MAFragmentsListener object to communicate with MainActivity
    • e.g private MAFragmentsListener listener = (MAFragmentsListener) context;
  • Allows user to input username into the search bar to find a specific user:
    • Makes a query to Parse database to find a user with the specified username, displays appropriate message if a user is not found.
    • Optional stretch: Allow user to search using an actual full name in addition
  • On click a user/profile:
    • call listener.toOtherProfileFragment(userID); to have MainActivity display the OtherProfileFragment
    • OtherProfileFragment is to be implemented by another issue!

• LoginFragment = the screen where the user enters information to get to the MainActivity!

• RegisterOneFragment = the first page of creating a new account. Requires: first name, last name, cpp email, password that meets all requirements, and re-typed password

• **NOTE: This issue is EXTREMELY similar to how it was done for the last project, the Instagram-copy app, and lots of sample code is already written from @jmnguyen1999 from doing the app frame, so it shouldn't be too bad! But seriously, don't feel pressured to finish absolutely everything if you don't have the time for it!

• Following the wireframes on README, create layout.xml files and implement Fragments for: "Login Screen", "Register 1 screen", and "Register 2 screen".

  • LoginFragment{ }:
  • Invoked by either: RegisterOneFragment or RegisterTwoFragment - in case user no longer wants to create account!
    • Takes: CPP Email and password
    • Attempts to Log in through Parse requests (just like in Instagram project), and handles it respectfully.
    • create instance of SAFragmentsListener{ }
      • private SAFragmentsListener SAListener;
    • attach this instance to StartActivity instance (which implements SAFragmentsListener):
      • SAListener = (SAFragmentsListener) context;
    • on click "Log in" button AND (current user's profileSetUp == true):
      • Intent to MainActivity
    • on click "Log in" button AND (current user's profileSetUp == false):
      • call SAListener.toProfileSetUp();
      • Purpose: to display the ProfileSetUpFragment instead since the user has not yet set up their profile!
    • on click "Don't have an account? Sign up now!" link:
      • Create a User object
      • call and pass into SAListener.toRegisterOne(User object);
    
    
  • RegisterOneFragment{ }:
  • Invoked by either LoginFragment - when user wants to start creating account
    • Takes info:
      • first name
      • last name
      • CPP email:
        • error check that email ends with "@cpp.edu"
        • initialize User's 'username' field = the string w/o "@cpp.edu"
    • If the User object passed in already has some info --> auto-fill into corresponding sections
      • Purpose: displays saved info to the user in the case that they already filled out these sections while creating an account but went back to this page to edit something
    • create instance of SAFragmentListener and connect in same way to StartActivity!
      • e.g. private SAFragmentsListener SAListener;
      • SAListener = (StartActivityListener) context;
    • on click "Already have an account? Login here!" link:
      • call `SAListener.toLoginFragment();"
    • on click back button (wasn't specified in the wireframe but should have one!):
      • call SAListener.toLogInFragment();
    • Confirms the password and re-typed password match EXACTLY
    • a new User object is created and POSTed to Parse database using the User{ } setter method (model Parse and java class must be created by Parse database issue person)
      • handle fail or success of Parse registration appropriately
    • create instance of SAFragmentListener and connect in same way to StartActivity!
      • e.g. private SAFragmentsListener SAListener;
      • SAListener = (StartActivityListener) context;
    • on click "Create account" button:
      • call SAListener.toProfileSetup(User object);

• For extra help on connections between interfaces, activities, and fragments:

  • You can see an example of how @jmnguyen1999 did her "Snapagram" this way with an in-class interface, under StartActivity.java and the StartActivity packaged Fragments!

• Create a new app in back4app titled "Wings".
  • Add all NSLJ members as Collaborators: "App Settings" on left toolbar --> "Collaborators" --> "What's their email?"
• Create all Model classes listed in README, in Database browser: include all fields
• Enter in some dummy data to test around with! Users and Buddies for sure!
• Create and implement a corresponding Java class for every Model. This includes implementing all fields and establishing getters and setters to connect to the online Parse database!
  • **NOTE: Some field types in the models are listed as a List<> because they NEED to be able to have different lengths, i.e different users will add a different amount of friends. But because Parse only allows Array types, you will have to list it as an Array in the database, but KEEP it as a List<> type when in Java! Arrays in java force a fixed size :(
    • this means, provide a setter method that converts the List<> into an Array when storing it in the Parse database!

• Create a new Worker class that sets the User's current location in Parse in the overrided doWork()
• Handle the Worker class as a part of the SendLocationWorker class
• Figure out how to execute the worker after the SendLocationWorker
• implement the Home Fragment's Dialog box

• UserProfileFragment = Displays the current user's info and allows certain personal features

• OtherProfileFragment = given a userId, displays the given user's public info and allows the current user to add them if applicable

• Follow Figma wireframe designs to create layout.xml files for the screens: "User Profile Screen" and "Other Users' Profile Screen" (which are almost identical)

• Connect and implement the UserProfileFragment:

  • Invoked by the bottom navigation bar
  • Displays profile info:
    • first name
    • email
    • rating (and how many total reviews)
    • Pin code (stretch: What's my pin?)
  • Log out - logs out the user
  • Ability to edit profile picture:
    • "Take a Photo" --> Intent to Android camera
    • "Choose from gallery" --> Intent to Android gallery:
      • Resource for help: how to intent to android gallery
  • On click "What's my PIN" link:
    • Dialog Box to ask for account password, then displaying the user's PIN
      • NOTE: Dialog Box is essentially a little pop up form or message that can take a small number of user inputs and act on it. It shouldn't be extremely hard to implement
      • Resource: Android Dialog Box Guide
    • Optional stretch story later: require more security here, e.g. security words, phone/email confirmation, etc

• Implement the OtherProfileFragment, cannot connect it yet though because it needs SearchUserFragment!:

  • will be invoked by SearchUserFragment
  • Uses a MAFragmentsListener to communicate with the MainActivity
    • e.g. private MAFragmentsListener listener = (MAFragmentsListener) context;
  • Expects to receive the userId of which User info to show! Here's how to receive the data from the MainActivity:
    • Resource: Passing data from Activity to Fragment
  • Queries for the User object corresponding to this userId
  • Displays this user's info:
    • first name
    • email
    • rating (and how many total reviews)
    • status of relationship with current user: e.g. "My Friends" or "Others"
      • easy to get current user: ParseUser.getCurrentUser()
  • On click "Add user" or some icon:
    • Add the userId to the current user's "friends" field (List)
  • Should have a back button (wasn't included on the wireframe):
    • On click --> call listener.toSearchUserFragment();

odjhafi aundf

👍 Nice work on the second implementation sprint! Excited to see your progress next week!

👍 Thanks for submitting your progress for this sprint! This is a big milestone as now it's all about adding optionals and additional polish to the app. Next week we go into the final sprint before demo day.

👍 Nice job on the wireframes! Wireframing is a common practice when building apps as it lets you create a blueprint for the app before writing any code. Having a really good blueprint that you can refer to throughout the rest of the project is a really valuable resource and will make it much easier to split up work across your team.

With the wireframes in hand, you should have a good idea of what your app will look like when you finish the project. Next week we'll jump into the data schema.

This one's a doozy.

• Resources found for Google Maps and things:
  • CodePath Guide for implementation of Google maps SDK
  • General Google Maps SDK overview
  • Google Maps Directions API
    • i.e. how to route
    • Here's a few step by step vids I found but I didn't actually watch them so:
      • Drawing route directions
      • Drawing route directions
      • Drawing route directions
  • Google Maps Places API - may or may not need to be used
    • can convert coordinates (lattitude, longitude) to place_id's
    • routing with place_id's allow for more accurate routes e.g. with just coordinates, only routes with nearest road
  
  
• Figuring out how to use Google Maps Directions API, Google Maps SDK, and any other tools needed to:
  • Display the map on the HomeFragment
  • Track user's current location, display it with a marker, and update the user's "currentLocation" field in the Parse Database on an asynchronous thread (or some other way to constantly check their location):
    • Resource: Android Studio by self can get coordinates
  • Allow the user to search for a destination and route to it
  • Display the route, including markers of User's current location and destination
  • Find the EST given by the Google Maps API of the route
  • Figure out how to test simulating going on the trip (e.g. just walking from one location to the destination, nothing about the buddy system yet)
    • Resource: CodePath Guide for Setting up and simulating locations with Google maps SDK:
      

Purpose: option to either dial police automatically, or contact all TrustedContacts

• intended to be a Dialog Box for easy access

Purpose: Display all potential buddies in a Recycler View and allow to the current use to choose one.

• instantiates a Buddy object, = represents an active user who currently wants a buddy (to differentiate between all other inactive users)
• Once chosen, go to PotentialBuddyFragment filled with the user's infomation and mapping of their current location and their intended destination.
  • on PotentialBuddyFragment confirmation --> some notification that Buddy Request was sent, back to ChooseBuddyFragment:
    • Creation of a BuddyRequest instance
    • num of buddyrequest sent increments and displayed somewhere
  • rejection --> go back to ChooseBuddyFragment

• invoked by the top nav bar, menu item
• Allows user to edit their profile and account information
• Uses a RecyclerView to list all the possible information the user can edit
  • on click an item, goes to another fragment
  • re-uses TrustedContactsFragment

• Email?

👍 Nice work on getting the data schema defined! Next week we jump into the first implementation sprint. You'll have 3 sprints (one week each) to complete all the required stories for your app and 2 sprints (one week each) to work on optionals and add polish. Let us know if we can help in any way!

👍 Great job on the first implementation sprint! The app is really starting to come together. There are 2 weeks left to complete all of the required stories so that you have an MVP (minimum viable product). The purpose of this is to get the minimum set of functionality implemented first and then focus on adding in optionals afterwards. This ensures you have all the basics in place before adding in the additionals and polish.

👍 Thanks for submitting your final GIF walkthrough! It's pretty remarkable when you step back and think about how far you've come in the course. 👏 We started with a simple tip calculator and ended with a fully functional app that you've built from the ground up.

Make sure to review the demo day tips as these will help you put together an engaging demo. Best of luck on demo day! 🎉