mit-dci / artistry Goto Github PK

First round basic endpoint code so others can build off of it-- build out own endpoint that does web scraping.

something fun for the homescreen, with images.

show welcome screen on first boot (without link to last.fm or payment info), and divert user to setup their account and learn the UI.

update UI to show payment info for artists (whether we have a payment address (color), how stale it is (hue), how trusted it is (! if not), what form of payment it is (ie venmo/bitcoin symbol). Could indicate when we have a payment address that is verified but that we can't pay because the user doesn't have (ie) bitcoin by greying out.

self explanatory.

endpoint should be queriable by artist mbid or artist name, and return a payment address array (ordered by artist preference) and optionally a certainty score and a last_verified date.

When displaying payment info associated with an artist on the 'payments' screen, we may also show contact info associated with the address and collect user feedback to send back to the endpoint about the user's belief that the payment address is legitimate.

Debug/finish image cache feature and make sure images are stored in between app open/closes.

add a dictionary of 'payment_type':'payment_address' to artist store.

look at some comparable apps and figure out how to lay it out slightly more intuitively.

have endpoint optionally give contact info for artists and a flag for whether they accept/want feedback, which will change the UI displayed to the user so they can say whether they trust the contact address provided.

an ordered array of trusted endpoints that can be rearranged in the store to reflect order of most trusted to least.

add in payment info (personal venmo wallet id, personal bitcoin key, etc) to payment store and corresponding visual

self explanatory.

pull payment info for artist from the artist_array, if not there go through and query endpoints and update artist_array if found, if not found simply ignore paying artist.

When found, call payment based on user preference first and artist preference second for payment mechanisms, assuming there is symmetrical payment information. Simple call to API.

Update past payments, adding a flag for 'successful_payment' or not, so we can look at the back-log of who was actually paid and who wasn't (and optionally set aside funds for artists that aren't paid).