Inspiration
Many of us have gone out on a night and have either spent more than we wanted to or have had a friend spend way too much money. It's never fun realizing you have less money, so we considered a responsible way to combat this issue for any and all events.
What it does
This feature allows people who are conscientious of their spending habits to create a budget specific to certain events where they only want to spend a certain amount. By checking the available spending amount in the user's checking account and ensuring the budget does not conflict with any subscription payments or take the user's available cash to a low amount, this feature lets the user define how much they are willing to spend for an event of their choice. While normal expenses will be restricted once you go over budget, emergency purchases will still be allowed such that the user will not be penalized for unfortunate circumstances or poor spending habits. In doing this, the feature helps users enforce spending restrictions in a way where they can help themselves if they want to.
How we built it
Using Capital One's Imagine Banking API, we imported its SDK into Android Studio. Then, we separated the different accounts of the customers into three activities: CreditActivity, CheckingActivity, and SavingsActivity. We then used Android's XML design to edit the page layouts of these three activities.
The Saving's Interactive button utilizes Android's intent to go from the button press to the the user's Savings account. The page displays the current balance of the customer's savings account.
Challenges we ran into
The biggest challenge we ran into was cloning the imported Android project into each of our laptops. Because of different OS's and different versions of Android Studio, the build gradle file wasn't functional in the other team members' machines.
In regards to the design, custom styles (i.e. color schemas different from the default project theme) were not usable. We then had to reset and go through each of the layout elements and set them to default.
Lastly, the Manifest file did not include permission to access the INTERNET, which further hindered compiling the gradle file.
Accomplishments that we're proud of
We are proud of our teamwork, within short amount of time we knew each other. We each contributed to coming up with ideas and on the day of were committed to changing short notice.
What we learned
We learned how to better work in a team and how to organize many moving parts of a team on short notice. We learned more about our weaknesses and the amount of work and effort needed to actually develop a fully functioning application.
What's next for BitbyBytes
If the feedback for this idea from Capital One is positive then we will continue to develop the application and fully flesh out a functional working android prototype and continue working in accordance with Capital One implement it in Capital One's current mobile application.
Log in or sign up for Devpost to join the conversation.