Good timing, BTC dropped from 1080€ to ~900€ today :-) I don't know if it's just a problem with my windows 10 installation but the currency (USD, EUR etc.) dropdown is not clickable. With tab- and arrow-keys I can switch to EUR.
I'll investigate this issue and will attempt to fix it.
This is cool, but I wish coincap.io was more transparent about their data sourcing. Which exchange(s) is/are they sourcing from? This data can't be coming from ShapeShift (the owners of coincap.io), since prices on coincap.io are in USD while you cannot trade in fiat whatsoever on Shapeshift.
Thanks :-) BTW you can change fiat currency in the app and on coincap's website as well.
This is cool, but I wish coincap.io was more transparent about their data sourcing. Which exchange(s) is/are they sourcing from? This data can't be coming from ShapeShift (the owners of coincap.io), since prices on coincap.io are in USD while you cannot trade in fiat whatsoever on Shapeshift.
Thanks :-) BTW you can change fiat currency in the app and on coincap's website as well.
Hm, I wonder if coincap just takes generic cryptocurrency prices and converts them at going exchange rates. I.e., the prices aren't 100% tradeable.
LOL, believe or not I was thinking of building a similar app (only for bitcoin), also FOSS, also simple drop-down from the menu bar with https://github.com/maxogden/menubar as base...
But my idea included react-stockcharts or react-sparklines... :P
LOL, believe or not I was thinking of building a similar app (only for bitcoin), also FOSS, also simple drop-down from the menu bar with https://github.com/maxogden/menubar as base... But my idea included react-stockcharts or react-sparklines... :P
Haha, it happens to me all the time. :p
Anyways, this is an open source application. Feel free to add features in it :)
Good timing, BTC dropped from 1080€ to ~900€ today :-) I don't know if it's just a problem with my windows 10 installation but the currency (USD, EUR etc.) dropdown is not clickable. With tab- and arrow-keys I can switch to EUR.
It is fixed in v2.2.1. Thanks for reporting the issue. :)