Setup the page that's shown after a user first signs up

[rishigupta9999]

I've created the NewAccount controller and view. You can start prototyping it there.

[phoenixxxx]

As described in the document, this page can be many things.

• Show stats about the shows you have been to.
• Show information about upcoming shows.
• Have a strong social component.
• Display stats about your feedback history.
• Display trivia about your favorite artists.
• Show you stats about what other shows/artists you might like
• Ask questions about your friends' tastes (turn this into a fun activity) --> For data gathering purposes.

For the MVP here are the key features:

• Group info:
  • Who are in your group (active/pending)
  • Basic group stats (count, common liked artists)
• Statistics that we have on you
  • Shows you have attended
  • So far from FB and Spotify (data sources will be added over time)
• Ability to provide more info
  • Text box: Tell us about your music taste
  • Simple survey style questionnaire (again for data acquisition purposes)
• Links from the web on what is going on in the music community (all manually updated by us)
  • Facebook/Twitter posts (public) from some known artists
  • Youtube links to music videos
  • Links to articles

Note: Technical limitations should not be the only factor to take into account. We need to establish whether there is interest on the part of the market, and for that we need to have some sort of appeal feature-wise.

[phoenixxxx]

At this point I am looking into how to spec the technical aspect of the feature. Some basic database aspect need to be in place. We need to have the Facebook/Spotify API setup, and finally the server communication for user input needs to be layered in. The page rendering should be the more straight forward aspect of the work.

• Database back end
• Facebook & Spotify API
• Ajax queries
• Bootstrap for page rendering

Note: There is already a big manual dev component (updating aspects of the page like selecting articles, links etc... will be done manually.)

Design-wise, this is where we get to test a lot of the user-newton interactions. Things like asking direct questions to the user about their musical tastes, etc... See how much info we can gather here. It is also the place where to can study group dynamics (ie: how to we leverage the group in order to maximize recommendation accuracy and ticket sales).

Most (if not all) of the info available in here will be sent to the user in the newsletter. That is a good way to ensure they are kept somewhat engaged, and can access this information.

[rishigupta9999]

Before the user has linked their Spotify account or anything like that. So a brand new user...we have to decide what to show them. Is it the "checklist" that I presented in the wireframes? Something else?

It will still take a bit of time to do the front-end also. Even if it's just running off dummy data.

[rishigupta9999]

Either way, you can paste wireframes or designs here. And if there are certain database fields or schema you have in mind, let me know on that also.

I will be setting up the Users table this week as part of #2

[phoenixxxx]

"Before the user has linked their Spotify account or anything like that. So a brand new user...we have to decide what to show them. Is it the "checklist" that I presented in the wireframes? Something else?

It will still take a bit of time to do the front-end also. Even if it's just running off dummy data."

I think 90% of the suggested data still applies. Most of the fields will be missing information (as we discussed) like the favorite artist, but it is ok. I like the idea of the page being the same, but the data getting filled up progressively as the user gives us more information.

[rishigupta9999]

We can do that as a starting point. And then let's see what some of the metrics such as bounce rate, or % who do the next action are.

[phoenixxxx]

Agreed

[rishigupta9999]

Closing this. Let's file more granular bugs now since the structure of the page is setup .