FoodMob

Eating out with friends made easy. This is the iOS portion of the application. The backend server is in FoodMob-Node.

HTML documentation of the functions and API can be found in the docs folder.

iOS Application

Features

• Find nearby restaurants with fine-grained criteria.
• Set up your profile including your likes and dislikes.
• Add friends to a search, which takes into account their likes and dislikes.
• Add parameters to a search to further filter restaurants.

Assistance for using the application can be found in Profile -> Help in the application, or in the FoodMob/Resources/help.html file.

Known Issues in Version 1.0

• Login/Registration: When rotating to landscape, the application does not lay out the views properly.
• Network: A slow network may cause the application to crash if many views are loaded at once.

Development

Build Requirements

• Xcode 7.3 with iOS 9.3 SDK
  • Current Swift version: 2.2
  • Targeted iOS version: 9.1
• Homebrew (http://brew.sh)
• Carthage (GitHub)

Getting Started

1. Install the two command line tools you will need if you don't have them:

   • Homebrew

   • Carthage using Homebrew:

     brew update
     brew install carthage
     

2. In this project directory, run

   carthage bootstrap --platform iOS
   

   This installs the library dependencies needed for this application.

3. Open the FoodMob.xcodeproj file using Xcode.

4. In the top bar, the scheme should be set to FoodMob, and the destination should be a simulator or device (i.e, not "Generic iOS Device").

5. Click the ▶️ Run button in Xcode to install to your connected iPhone or Simulator.

Adding new libraries

Please follow these procedures for adding new libraries.

1. Libraries must be licensed permissively. No GPL/LGPL crap. MIT and Apache are good ones.
2. Libraries should be available as a framework (dynamic library).
3. Libraries should be approved by Jonathan (@jonjesbuzz). Open a GitHub issue or contact him on Slack.
4. Libraries should be available to download using Carthage.
5. It would be nice if the library is written in Swift. (This effectively requires #2 for technical reasons.) Objective-C libraries are allowed, but Swift libraries tend to be nicer to work with in Swift (obviously) and tend to be more modern.

Images