Week 7 - FoodOn Goes Web-Based (O/S,Networking)

    This week marks the last developmental blog post before the wrap blog post for next week. That means that I should tie up all loose ends with my FoodOn app. Last week I mentioned briefly about an online aspect that could trailer on along with the app itself.
    Basically what this online experience would be is a way for people who don’t have the mobile capabilities of a smartphone to still enjoy the functionalities of the FoodOn app. What the website will first do is verify your identity with an online id username that is tied to your phone number which will allow restaurants to at least contact you for reservation and cancellation purposes and once you give our password that is also tied to your phone number, you can then browse the website which will allow you to do all the same things that you can do with the mobile app. You would be able to track your caloric progress, you would be able to view recommendations based on your previous selections. And of course, you would be able to access a restaurants menu through the website.
    This app ties in with last weeks lecture because it will be able to work on several Operating Systems. Because it is a web/mobile application, it will be available to any operating system that can access a flash-enabled website. The consumer’s info will also be safe because of the SSL protocol that would be implemented into the website so the restaurant/consumer relationship would be kept between the consumer and the provider.
    Overall, this app would be accessible on any Operating System including both of the major mobile operating systems, Android and Apple’s iOS. This will allow maximum implementation and proliferation of this software allowing the maximum amount of people who access the internet and use their phones to be exposed to this application. As a result, I hope for the overwhelming success of FoodOn.