1. de’Bill Final Project – android app Team Members: Ilya Shamis, Daniel Grinberg, Nirit Lapidot Supervisor: Prof. Moshe Sipper

2. Motivation W e had all gone through this experience at least once in our lives: You go out with a large group of people, having a great time, until an extremely long bill comes and either you spend time looking for the things you ordered, or some people left early and didn’t pay their whole part of the bill, and you are forced to put some extra money. All of those situations are exactly what gave us the idea of creating de’Bill : an application that makes its users' lives much easier providing them with a personal service.

3. de’Bill……  Ensures that every member of the group pays its orders  Makes it easier for the client to see its personal bill  Provides a personal menu directly on the client’s smartphone  Allows members of the group to pay for others without asking

4. How it works The application provides its users with the following features:  Login  Register  Choose a place (restaurant, pub, etc.)  Create a group  Add/Remove members  Order from the place’s menu  Pay de’Bill!

9. The Restaurant side  In order to make our application functional in the real world, we added an application for the restaurants to be able to create/edit their details/menu.  This app is also connected to the main data base, so each change made by it, is immediately shown to the clients.

10. How did we do it?  The implementation of the app is Java based.  Each screen in the app is basically an.xml file. The code determines the visual properties: the color, size, font and location of each item seen on the screen (buttons, lists, text-fields, etc.).  Each.xml file is related to an Activity written in Java. Activity class is a pre-defined class in Android and every application which has UI (User Interface) must inherit it to create a window. The behavior and features of every item on the screen is managed by this java file.  This app deals with different kind of data – user details, restaurants menus, groups details, etc. We chose to store and handle this data using an SQL database. We use a java class (SQLHandler.java) that communicates with this database, by creating SQL queries that create/update/remove/read entries from the DB tables.

11. Behind the scenes a look at the database USERS TABLE GROUPS TABLE RESTAURANTS TABLE

12. Summing up We believe that an application used on a daily-basis should be as simple and as easy to use as possible. We hope that we have managed to do so in de’Bill’s implementation, and that we have succeeded in solving small but irritating misunderstandings Ordering a bill: Before de’Bill And after