A web application to track financial portfolio growth. Uses free and open APIs to fetch real-time market data to store in an online database. Produces a graph updated in real-time.
Stretch goals are (1) Introduce a user-authentication mechanism
Take a look at our Figma designs here
The work is distributed among two developers in this order:
- Developer-1 - Tab-1 - Data
- Developer-2 - Tab-2 - Graphs
A week before the end (i.e starting Jul 26), the focus would be on performing final integration, deployment and preparation of presentation with Q&A readiness
- There is no UI for a user to enter any data and retrieve at a later date
- There is no UI for a user to determine how his portfolio value has been fluctuating since the purchase of any constituent stocks/ETFs
- There is no automated batch job that retrieves current stock prices to populate a database
- There is no database to store stocks/ETFs a user has in their portfolio and to hold values retrieved by batch jobs
- Setup IDE for local development (UI, API)
- Setup DB locally for reading/writing data
- Setup Git locally for interacting with Github
- Start working on UI (tab-1/tab-2) and send PRs
-
Tab-1: A "data-entry strip" at the top should write data into database in the following format:
- Ticker
- Name (auto-populated at a later stage)
- Security Type
- Quantity
- Purchase Price
- Purchase Date
A tabular form listing the above fields is populated with data from database. Should be scrollable
- Tab-2: A graph should be available with some sample data populated in a table in database. Start working on batch job to populate data from Finnhub
- Tab-1: Finalize working on the scrollable tabular form.
- Tab-2: Finalize working on batch job to populate database with data from Finnhub
- A presentation is prepared
- App is deployed in AWS EC2/Heroku/a VPS
- Setup IDE for local development (UI, API) - DONE
- Setup DB locally for reading/writing data - DONE
- Setup Git locally for interacting with Github - DONE
- Start working on UI (tab-1/tab-2) and send PRs - Moved to Jul 12 - Jul 18
At this time, you can run this locally with a DB setup. Our goal is to have this deployed in a publicly accessible web server during the week of Jul 26 2020.
Please open an issue here on Github or talk to us on Gitter to be informed when we go live. We're excited to talk to you!
We're on Gitter!
