So, I've just started to do some work and I quickly realized that the only way to really get an idea for the required components of the app, is to have real data.
Of course, we can't get real data right away, but this is a task for @ethguo or @advait-m. Take some time to go through yelp the yelp database, and identify the properties they have for each business object. Additionally, start to brainstorm some ideas as to what exact information is going to be displayed on the details page.
Ultimately I want to see a list of mock businesses and deals. Make sure they aren't carbon copies of each other, each business will probably have the same static properties, but deals by nature have a chaotic list of properties they could or could not have given the nature of the deal.
For example, a storewide sale would be very basic, the only information that would be non-null is likely the deal name, the source store, the duration, the status (is it live or dead), and the quantitative specifications of the deal itself.
The aforementioned style of deal is the kind that store owner's who just want to post a basic add would take advantage of.
Alternatively, a store owner could potentially need to specify specific products that the deal includes, in which case you'd need a firestore subcollection under deal called items. In which each item would contain for example an image, rating, description, Array<comment/reviews>, normal price, sale price, stock etc.
There is a lot of room for creativity, and I believe the best way to inspire us to add features is to think like a business owner and consumer and create a series of templates for all of the data types which we'd like to take advantage of.
So, I've just started to do some work and I quickly realized that the only way to really get an idea for the required components of the app, is to have real data.
Of course, we can't get real data right away, but this is a task for @ethguo or @advait-m. Take some time to go through yelp the yelp database, and identify the properties they have for each business object. Additionally, start to brainstorm some ideas as to what exact information is going to be displayed on the details page.
Ultimately I want to see a list of mock businesses and deals. Make sure they aren't carbon copies of each other, each business will probably have the same static properties, but deals by nature have a chaotic list of properties they could or could not have given the nature of the deal.
For example, a storewide sale would be very basic, the only information that would be non-null is likely the deal name, the source store, the duration, the status (is it live or dead), and the quantitative specifications of the deal itself.
The aforementioned style of deal is the kind that store owner's who just want to post a basic add would take advantage of.
Alternatively, a store owner could potentially need to specify specific products that the deal includes, in which case you'd need a firestore subcollection under deal called items. In which each item would contain for example an image, rating, description, Array<comment/reviews>, normal price, sale price, stock etc.
There is a lot of room for creativity, and I believe the best way to inspire us to add features is to think like a business owner and consumer and create a series of templates for all of the data types which we'd like to take advantage of.