MaverickGDN03
commented
1 year ago • User journey
○ To user stories
• Blue thing (ticket thing on the top)
○ Like a milestone
• Can put backend functionality in MVP
• Rating wise, outside of MVP
○ Make our customers rate the products rather than scraping the ratings
○ But how do we know that customers have rated the product without buying
○ Later on, after MVP though
• For the personalized experience
○ AI cat. Based on previous user searches etc
• Ads
○ Product they haven’t seen based off items they have searched for etc
○ AI cat as well
• Special Promotions
○ Promotions as a wishlist item
§ When a product is on promotion, we can notify users
• Sellers
○ List of categories that we support
○ We would need to vet each website and see if we can scrape them
○ Seller auth
§ Ensure that sellers are good candidates for scraping
□ Find info about the business
§ Checkboxes instead of a text input
□ Wants to restrict the seller's ability to choose a certain amount of products
§ Make sure they are in SA
□ Easier to implement product wise
• Want to make sure that what's on the homepage helps to make sure customers find what they want
○ In a carousel
• Similar products
○ Doesn't have to always be AI
• Tensor flow
• Pytorch
• Product catalogue from the seller
• Ratings on a seller
• Follow a seller
○ On the homepage. Get all of the products from a seller
○ Adds to a personalised experience
○ Notifs from sellers that you have favourited
• Customer analytics
○ Conversion rate between clicking a product and going to the sellers websites
• Want the seller to have a good user experience , just like customer
• Customer notifying seller that there is an issue about their product
• Sellers get notifications aswell
○ Customer queries
§ Send a push notif
□ See a dropdown, a list of queries
○ Notifs if they verified or not
• Seller inventory
○ Sync their webpage again
§ Of whole website
§ For a single product, just do a manual entry update
§ What happens to the manual inputted data is it gets synced again?
• Bake analytics into data layer
○ Need to make sure we log the info
○ e.g. from homepage to product page
○ From product page to their website
○ Baked into API layerDjango admin panel for staff portal Need databse for this though Structure of our models
After seller details and verification Need to focus on scraping
SRS doc: We mentioned NoSQL instead of Relational Django creates models, tables We can use these models to store in database Can use Django tables to store in tables When we scrape and store, we wanna use our models and train our data
Figma design for form completeion
○ Form completiton
○ Staff portal is already created
§ No need for figma designs for that
• Domian diagram or UML diag , more refined in the srs doc
○ Similar to UML, higher level than UML
• Context diagram is similar to use case
○ In the miro docFriday • Figma design to be completed • Update of the SRS doc with new requirement • Architecture doc • Models for Seller profile
Date: day_name, DD MM Time: 15:00 - 16:30