"ENDRSD" is a capstone project that was built as a centralized location for Lambda School students to access track-specific career endorsement requirements, as well as provide students with a fun and engaging way to track their career endorsement progress.
Demo the app by downloading it from TestFlight.
| Alex Mata | Sameera Roussi | Victor Ruiz |
|---|---|---|
 |
 |
 |
 |
|
|
- Students can create their own user accounts and passwords on iOS devices
- Users are able to login & logout on iOS devices to protect their career endorsement information
- With proper credentials, students are able to view a list of their track-specific career endorsement requirements on iOS devices
- Students are able to track their overall endorsement progress on iOS devices, as well as stay up-to-date on the progress being made towards individual requirements for endorsement
- Students can access static resources pertaining to specific endorsement requirements on their iOS devices, such as Airtable forms and lecture videos
- A self-contained token which has authentication information, expiration information, and other user properties.
- JWTs don't have sessions to manage (stateless).
- No database table is required, which means fewer database queries.
- Can be used across multiple services.
- Protects against 'rainbow table attacks'.
- Resistant to brute-force search attacks.
- iOS 8.0+
- Xcode 10.3
- Cocoa Pods
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
Please note we have a code of conduct. Please follow it in all your interactions with the project.
## Contributing
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
Please note we have a code of conduct. Please follow it in all your interactions with the project.
If you are having an issue with the existing project code, please submit a bug report under the following guidelines:
- Check first to see if your issue has already been reported.
- Check to see if the issue has recently been fixed by attempting to reproduce the issue using the latest master branch in the repository.
- Create a live example of the problem.
- Submit a detailed bug report including your environment & browser, steps to reproduce the issue, actual and expected outcomes, where you believe the issue is originating from, and any potential solutions you have considered.
We would love to hear from you about new features which would improve this app and further the aims of our project. Please provide as much detail and information as possible to show us why you think your new feature should be implemented.
If you have developed a patch, bug fix, or new feature that would improve this app, please submit a pull request. It is best to communicate your ideas with the developers first before investing a great deal of time into a pull request to ensure that it will mesh smoothly with the project.
Remember that this project is licensed under the MIT license, and by submitting a pull request, you agree that your work will be, too.
- Ensure any install or build dependencies are removed before the end of the layer when doing a build.
- Update the README.md with details of changes to the interface, including new plist variables, exposed ports, useful file locations and container parameters.
- Ensure that your code conforms to our existing code conventions and test coverage.
- Include the relevant issue number, if applicable.
- You may merge the Pull Request in once you have the sign-off of two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.
These contribution guidelines have been adapted from this good-Contributing.md-template.
Distributed under the XYZ license. See LICENSE for more information.