fredmp/cryptocurrency_valuation_spa

A tool to help users create their own alt coins valuation rules

Cryptocurrency Valuation Tool

This is a simple project that aims to provide tools to help users create their own rules to evaluate cryptocurrency assets (alt coins) and organize their assets.

• Max price is an initial info based on BTC market cap (dominant coin) and the target coin supply. Basically: What would be the price if this coin had the same market cap as BTC?
• Potential growth is the difference between max price and current price
• The user can create custom valuation settings
• Once a coin is tracked it's possible to rate it based on the valuation settings previously defined. These rules will affect the potential growth to generate the expected price and expected growth

It works by accessing cryptocurrency_valuation_api

The data comes from the public CoinMarketCap API. It's updated every 15 minutes and respects the usage limits.

Once yarn is installed you can run, build and deploy it by using:

yarn dev
yarn build
yarn deploy

Next (possible) steps

• Add unit tests
• Add e2e tests
• Apply some refactoring to extract code to specific components
• Improve assets page to allow the user to register not only the amount but also when a coin is bought or sold and associated costs. That will provide a more accurate overview as well as information such as mean price
• Create an initial page to show in the root path. It could display news and useful graphs for example

Contributing

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request

Legal

Cosmos Tecnologia © 2017-2018

@fredmp

Licensed under the MIT license

cryptocurrency_valuation_spa's Issues

Bug when an asset is added

• When we try to add a new asset it sometimes doesn't work (more often, when it's the first one after opening the page)
• Sometimes the highlight effect is not triggered on the correct asset
• Besides the bug it would be great to keep the recently added asset at the top of the list (until the user clicks to reorder it or re-opens the page)

Add tooltip (or modal) to explain the concept of max price

Use svg sprites

Instead of requesting all images to the server, it's better to use a file with all SVG images (sprites).

Improve assets page

Allow the user to register not only the amount but also when a coin is bought or sold and associated costs. That will provide a more accurate overview as well as information such as mean price.
It will be necessary to change the API as well.

Add icons to currency and tracked tables

Add link to password recovery

Add unit tests

Use placeholder for not found icons

Add e2e tests

Improve deploy process

Currently, to perform a deploy we need to keep the dist folder in the repository (removing it from .gitignore). It doesn't seem to be a nice approach to track these generated files.
This solution can be a better option: https://dev.to/jmbejar/how-to-quickly-deploy-a-vuejs-app-to-heroku-5b0f

Fix icons location

Send signup email

Icon to untrack coin in tracked table and details

Create an initial page

It could be used as the root path whether the user is logged or not. If user is not logged it could display news and useful graphs for example. When it's logged it could add more specific information related to the assets and tracked coins of the user.

SVG is using an incorrect width on Firefox

Apply some refactoring to extract code to specific components

Some components have too much responsibility. Probably part of their code can be extracted to specific components. For example the modal dialog in ValuationSettings.

Add Powered By section in footer listing APIs and OS projects being used

Fix collapsed menu

Menu is broken when screen size is small

Send user to home when localStorage token is expired for a long time

Token is valid for 1 hour. A new token is provided every time user makes a request. If user is idle for more than 1 hour we should clean up localStorage credentials and:

1 - Send user to Home when idle for more than 5 hours
2 - Send user to Login when idle between 1 and 5 hours

Let's say: when user forget the tab idle for more than 1 hour, login screen is shown. But if user tries to access the site after a long time, home screen is shown.