You can find the deployed project on Apple TestFlight.
| Isaac Lyons |
|---|
 |
| Tyler Christian |
|---|
| Nick Nguyen |
|---|
| |
You can find the deployed project on Apple TestFlight.
Budget Blocks is a personal finance app that brings the Envelope System to your smartphone so you can better manage your money and track your expenses.
Users can create a block that and select a category for it to be put under and then set how much money they want that block to be budgeted to. for example: When i sign in and create a budget I can select the category "Food and drink" and give that an amount of how ever much I think would be good and everytime i make a perchues I can go into the app and put the date i made the purches how much it cost and an optinal discription of what i bought then when I save that transaction it will put it into the right category and a progress bar will be visiable showing a visual of how much money I have to spend in that category till I have spent to much.
- Connect your bank account with Plaid
- Create goal to budget per blocks
- iOS 13.0+
- Xcode 11
- Carthage
- Swift Package Manager
- Note when first cloning this into a project be sure to run the command in terminal Carthage build in order to remove any errors you might start with
Plaid Link iOS SKD allows the user to connect a bank account to their Budget Blocks account. Requires the PLAID_PUBLIC_KEY environment variable to be set.
Okta is used for authentication(sign in/ sign up) and any other custom features to be added later on.
SwiftyJSON is used for easily encoding and decoding JSON for network requests.
KeychainSwift is used for easily storing login credentials using Apple's Keychain.
SVProgressHUD is for displaying elegant HUD when loading data.
Lottie is for beautiful animation.
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.
See Backend Documentation for details on the backend of our project.