Subscription Saver

Inspiration

Subscription services have been overwhelming and overspending teens and college students for many years now. With the crazy amount of streaming services that are available and pushed onto us there are many subscriptions that are often forgotten or that go unused. We wanted to make a service that takes all subscriptions from your banking invoices and compile them in one place to simplify it for the users.

What it does

Subscription Saver uses an API linked to your Capital One bank account that will track and note down all information about every recurring subscription found. Unlike other subscription trackers, this will break it down into categories of what your subscription falls into as well as all of the information that is possible to gather. Each subscription will show the date it is paid, the payment cycle it is on (annually, monthly, bi-weekly, etc). We took this information and presented it all in tables that are easy to read and easy to present to customers.

How we built it

We based our app off of the Capital One Mobile App for simple implication. We built a prototype that shows the functionality of our app, as well as a prototype that shows the desired UI of our app.

Challenges We Ran Into

Implementing the same service on a separate app or third-party platform, working with user sensitive and private data, how to track unused services, how to implement built in app usage data from apple, how to tracks Subscriptions paid with a different card.

Accomplishments that were proud of

Relaying our service through Capital One’s app itself Creating a clean and concise front end interface Getting everything done while still attending all of our desired workshops Tackling a challenge presented at the Hackathon by a company we love

Tracking Apps

In order to better aid users from unused services, we would keep track of their device’s app usage history to notify them of services they can consider canceling from lack of use. This feature would be available on both IOS and Android and integrated within the Capital One Mobile app.

Within the Android Platform API, there are functions that allow you to keep track of the use history of apps. Such as when they are in the foreground, background or unused. Using these functions, we keep track of all applications linked to a subscription service and determine when the app was last opened. We would be able to display to the user the last date that they used an app so they can better determine whether they need a particular service. If the app detects that 3 months have gone by without being opened, the user would be altered that the service may potentially be unneeded so they can cancel it.

Categorize Apps

Using this functionality, we can categorize the services based on how much the apps have been in use. Thus, they can see their most frequently used, moderately used, and least used services. In order to gain access to the usage history, the user would have to enable the app permissions that let us track the device.  


What We Learned

Working with Apple and Android data usage to collect data How to get data extracted from bank payments UX Design and implementations Figma design

What’s Next We would like to expand to other API’s that can provide data usage for devices outside of mobile. This being devices that use streaming services via Amazon Fire Stick’s, Roku’s, etc. Also implementing our better looking interface onto the mobile app itself.

Built With

• editorx
• figma