Difference between revisions of "Grocery Guru Log"
Jump to navigation
Jump to search
Annamcossio (talk | contribs) (edit log) |
m |
||
| Line 40: | Line 40: | ||
*each member of our group, without communicating with the others, sketched an outline of the design we envisioned for our application. We then compared each of our designs and compiled our favorite parts of each one. We will use our compiled outline as a guideline for our application. | *each member of our group, without communicating with the others, sketched an outline of the design we envisioned for our application. We then compared each of our designs and compiled our favorite parts of each one. We will use our compiled outline as a guideline for our application. | ||
*each member of our team downloaded multiple barcode scanning applications to our mobile devices and tested which one ran the most smoothly. We did this by testing the scanner with products from WashU dining facilities as well as from local grocers | *each member of our team downloaded multiple barcode scanning applications to our mobile devices and tested which one ran the most smoothly. We did this by testing the scanner with products from WashU dining facilities as well as from local grocers | ||
| − | *each | + | *each member continued to study the Swift lessons provided by Xcode |
| − | *set up a meeting with Humberto | + | *Maggie obtained a list of all the custom labels for Paws 'n' Go premade items with the names of the items and barcode numbers |
| + | *set up a meeting with Humberto for our first project proposal | ||
Revision as of 03:06, 28 February 2017
Contents
Week of Jan. 23 - Jan. 29
- created our WikiPage
- brainstormed ideas regarding nutrition, groceries, and efficiency
- considered creating an iPhone app that reads the barcodes on food products, and used the codes to help the user live a healthy lifestyle
- talked about the possible applications a health-related iPhone app could have in hospital use
- decided to instead make an iPhone app that aids a shopper as they make their way through a grocery store, such as Schnucks
- brainstormed a list of functions our app could perform that would aid the average shopper: speed through the store, ease in finding products, map of the store, what products are available for purchase, how long their shopping run will take, etc.
Week of Jan 30. - Feb. 5
- the three members of our team met up on Wednesday to draft an outline of our proposal
- drafted an overview and brainstormed a list of challenges, objectives, and a budget
- we were assigned Andrew O’Sullivan as a TA
- met with Andrew on Thursday and finalized each the components of our proposal (mentioned in previous bullets
- he helped us brainstorm ideas for our demo in order to make it interactive
- with Andrew's help, we learned the basics of how to create an iPhone app, including the possibility of needing to obtain a developer's license
Week of Feb. 6 - Feb. 12
- met with Andrew on Tuesday to discuss problems with our proposal
- added the challenge and the objective to make our app able to scan a limited number of barcodes on grocery items, so that our project is able to carry out a demo rather than a simulation
- Maggie researched app development and started working on an app developing lesson provided by Apple https://developer.apple.com/library/content/referencelibrary/GettingStarted/DevelopiOSAppsSwift/BuildABasicUI.html#//apple_ref/doc/uid/TP40015214-CH5-SW1
- Amelia researched different apps that have similar capabilities to our idea, including the Schnucks app
- Anna edited and revised our proposal
Week of Feb. 13- Feb. 19
- this week we addressed the problems Humberto brought up with our proposal
- we switched grocery stores so that we can have access to a list of all the products and the UPC codes
- we added access to an amazon cloud database to our budget to store the data that our app will utilize
- updated the project proposal to explicitly say what the app interface will look like
- updated "time" to an approximate time that will be spent in the store to account for users not following the routes perfectly
- this week all of the team members were tasked with learning swift language and completing a tutorial that teaches how to apply swift to xcode to create an app interface
- we used these two links: https://www.airpair.com/swift/complete-guide-to-swift and https://developer.apple.com/library/content/referencelibrary/GettingStarted/DevelopiOSAppsSwift/
Week of Feb. 20 - Feb. 26
- we met with Andrew on Tuesday and made additional changes to the objectives of our project. These objectives are as follows:
- we will now be using Paws 'n Go instead of Schnuck's; therefore, we can better track the inventory of the store and have easier access to the products and their barcodes
- we decided the primary goal of our application will be to provide the user with an approximate total cost of their shopping list
- each member of our group, without communicating with the others, sketched an outline of the design we envisioned for our application. We then compared each of our designs and compiled our favorite parts of each one. We will use our compiled outline as a guideline for our application.
- each member of our team downloaded multiple barcode scanning applications to our mobile devices and tested which one ran the most smoothly. We did this by testing the scanner with products from WashU dining facilities as well as from local grocers
- each member continued to study the Swift lessons provided by Xcode
- Maggie obtained a list of all the custom labels for Paws 'n' Go premade items with the names of the items and barcode numbers
- set up a meeting with Humberto for our first project proposal
