This dependencies are seriously slowing down our build time. We should remove them as we do not need them now. Moreover, we can write most of the tests as unit tests that are not dependent on Android Framework, so they probably will not be needed at all.

Create a Fragment that will allow selecting a meal from 10 - 20 last eaten. It should be accessible from MealFragment and allow both selecting and editing.

Reuse existing popup menu used in DayFragment. It should work in the same way.

There is a lot of code duplication in SQL-speaking objects. Create a set of objects that will take care of complex mapping.

Complete this fragment by creating its layout that will show list of available months with years division. Add new classes related to this view as needed.

It should allow adding FoodPortions to a given meal. It must reuse existing portions, adding new ones only if necessary.

Create ViewModel for ProductDefinitionFragment needs. Complete models logic where it is needed.

Create landscape version of layouts. If a portrait version looks good enough, do not change it, but remember to make it scrollable if necessary.

If day is not yet created it should be created after weight is given in mentioned above fragment. Its id should be given to DayFragment.

Minimal json containing categories and food products as data source is needed. It should not have many entries, as it will be extended later.

Category's food definitions should be moveable and deleteable. To do that, logic in related models and view model need to be added. Moreover, reusable popup menu need to be created and used in CategoryFoodDefinitionsFragment.

Get current/meal time from view model and setup NumberPicker properly. It also needs proper logic for listening to changes and updating meal time accordingly. Adding new food to meal and loading list of it should be handled as well. Each item should be deletable and editable. Create reusable component as popup menu for that.

Create ViewModel for GoalsFragment that will allow reading and saving goals from SharedPreferences. If needed, create new models for that purpose.

Create a way to instantiate InformationDialog with a title suggesting that an error had ocurred. Use it in every fragment that has callback to Result.

It will often be the case that user may want to change nutritional goals only for a given day. Add this functionality to DayFragment.

Simple communication mechanism that will allow fragments to respond to specific events needs to be created. It should probably be placed in RootView interface.

We need an object that will simplify and enhance Android Cursor usage.

Button for adding ProductDefinition in CategoryProductsFragment and according functionality in ProductDefinitionFragment is needed.

It should implement iterable instead of having next() method that returns next row, which is often very difficult to use. Refactor all classes using it

CategoriesFragment layout need to be created. Then data from its viewModel need to be used to draw its full view.

Create its layout that should look like CategoryFoodDefinitionsLayout, but it should display all of the food items without splitting them into categories. It should enable searching, adding new definition and redirecting to FoodPortionFragment on clicking food item.

It should allow updating meal time, loading meal, refreshing its content and deleting it from day.

Its layout should show list of days sorted by date with month statistics at the top. Each item in the list should be clickable and show popup menu with details/edit options. Create viewModel that will allow this, add/refactor models as necessary.

Currently, if we go from DayFragment to MealFragment and edit it, former does not know anything about it and is keeping old data. Message that MealFragment is receiving from FoodFragment needs to be propagated up.

Create popup menu that will allow to choose from these two options. In both cases show warning to user.

Every day meal is lacking last food data. Investigate queries made by DayViewModel.

Complete mentioned aboved Fragment layout and create its bare bones viewModel that will only return data by now. Layout should include search engine, its functionality will be implemented later. Code to Categories and Category need to be added to complete this task.

Create class that will format double according to rules:

• if it is an integer, do not show reminder
• else show as many digits as it was configured in a constructor

The way that asynchronous processes are called is too complex and , in case of returning Result, full of boiler plate code. We need object/objects that will make it simpler. Lifecycle awareness and making sure that callbacks are always called on main thread is also needed.

Complete mentioned above view models. They just have to return list of years/months available. Create new models that will fetch this data from database and views for displaying them. It needs to be possible to go from year to its months.

In MealFragment check if created/updated meal does no contain any food. If not, delete it. Functionality should belong to MealViewModel, call should come from Fragment onDestroy().

Before creating new food definition make sure that it does not exist in deleted state. If yes, just change its state and update values.

Currently, history stack, from main menu, is always -> years -> months -> days. It does not have sense if user have short history, so it needs to be flatten in that case.

Set up travis script that will build repo on every commit and start emulator for future tests.

Create its layout that will display food name, calories, protein and make choosing portion size comfortable. It should also calculate food nutritional values on portion change.

Create its layout that displays list of food and editable time. Items should be clickable and link to FoodFragment, time component should be implemented using NumberPicker. It should also have button for adding new food to a meal.

Most of food products and all categories will come from database.json. We need classes that will read this file and populate database properly, if it does not exist.

This fragment needs layout and input validation logic.

Fill this viewModel with logic. If needed create new/complement existing models.

Draw proper progress value in DayFragment. Change text color to red if calories goal was exceeded.

Refactor its layout so that it shows list of food for each day's meal.

Currently day goals are set in a separate view, which can lead to current day not having up to date goals. In GoalsFragment, if current day exists it should be updated.

Create GoalsFragment layout that will display weight, calories and protein goals. It should also allow to edit them.

Complete this file by adding the most frequently used food categories and its products.

Refactor this Fragment so that it is possible to create it without giving neither food_id nor category_id. In this mode Spinner with Categories should be displayed. Change layout and viewModel as needed.

DayFragment needs to allow updating and deleting its meals. It should be done by using PopupMenu, that needs to be created as separate component. Add needed logic to DayViewModel and to related models, if necessary.

Use WeightDialog for updating weight for a given day. Go to MealFragment for adding new meal to a day.