project 3 – part 3

  • Will the acts of storage and retrieval be voluntary or involuntary?
    • The acts of storage and retrieval would be involuntary because our app will provide a real time log of what people are ordering in restaurants. If it was voluntary, the results would be skewed and not an accurate representation of data.
  • Can items be stored and retrieved by just anyone?
    • Yes items can be stored by anyone in order to provide an open app that is inclusive to anyone wanting to see what foods are most popular at the restaurants near you.
  • Will personal identity be stored along with items? Or will items be storedĀ and retrieved anonymously?
    • our interface will have anonymous “users” that will not disclose any information besides what they ordered and the cost of their meal; one does not even need to create a “profile” to use the app.
  • Is your design intended for routine use, or one-time, ephemeral use?
    • This design is intended to be used however much the user wants, so in turn the answer would be that the user can use it routinely and watch the transactions happening in restaurants near them like a stocks app, or for a onetime use to see what they want to order in that one moment.
  • How much time will pass between storage and retrieval?
    • This app will have an almost instant retrieval of data proving to be the fastest and best data to provide information in real time. This is the biggest appeal to our app.
  • Will items expire, or be always accessible?
    • The items will be stores in a log of month to month and eventually show up as a chart yearly. Almost like a report on each individual restaurant. The user can access this data to see the seasonal shift of products sold in each establishment.
  • Will the act of storing or retrieving be obvious to others watching?
    • This app will be a very low- key viewing experience and others around you will not be tuned in to if you are using it or not. All of the data being retrieved, stored, and logged is happening behind the scenes providing a quick and easy experience for the user.
  • What will be the nature of the relationship between storer and retriever?
    • There will be almost no relationship between the storer and retriever, meaning that one is purely adding information to this data collection and the other is a spectator of all the “storers”.
  • Are they the same person, strangers, friends?
    • They could be friends, strangers, or anywhere in between. This is the nature of keeping the information logged anonymous, which in turn provides no bias to the user.
  • Is your device intended to be used alone, or in groups?
    • Our device could be used in a group but is intended to be used by one user on one screen. If a group uses it they would have to look at one screen together or have their own.
  • How legible will geo-spatial location be in your project? Will the userĀ at either end be expected to pay active attention to her geo-spatial location?
    • The user would have their geo spatial location on the app to view and would have to be “in range” with in reason in order to retrieve data for restaurants.
  • Will you approach geo-spatial location as an absolute or relative grid?
    • Our device will approach geo spatial location as a relative grid because it will be based off of the users location and what restaurants are near them in order to retrieve data.

Leave a Reply

Your email address will not be published. Required fields are marked *