If one enters a sublevel of any item in the bottom navigation bar, i.e. a fragment is added to the stack, it is not correctly removed if one directly navigates to any other item in the bottom bar before clicking back on the added to stack fragment. This leads to unexpected behaviour leaving the back arrow in the top bar even though one is in the main fragment.

Checkboxes are ticked of down in the list when some checkbox higher up in the list is clicked.

Recipe Title is not set when selecting a recipe from generate recipe view.

Is your feature request related to a problem? Please describe.
The application, when in loading state (where ever in loading state), does not serve any kind of description of what is going on at the moment.

Describe the solution you'd like
Some kind of information should be given to the user when parsing the receipt for example, updating groceries, etc.

Refactoring

Description

Move 'my groceries' to Home screen

Files to process

• fragment_my_kitchen.xml
• MyKitchen.kt

Why this is necessary**

Improvement on GUI and UX, avoidance of two clicks to get hold of own groceries.

Refactoring

Description

In Scanner.kt we need to check which device is in use, to only sleep the main thread when on Huawei devices since a known issue with those is that the abortCaptures() is not async.

Files to process

• Scanner.kt

Why this is necessary**

To only set a timeout when using a Huawei phone.

Application crashes when one triggers an internet request (which will manipulate the view), and then quickly manually changes view, before response from is handled. The response triggers a view change and makes the application crash since the user is not in the "correct" view.

When grocery from shopping list is removed, is should be added in a "already bought"-list under the regular shopping list.

Enable editing and selection of rows to include in the addition of groceries.

Including the add-functionality.

Is your feature request related to a problem? Please describe.
We're fetching each recipe on click in the recipe list view, which adds up to unnecessary request since we're paying per request on the API. Additionally, it's unnecessary to fetch all recipes again when pressing back from a recipe instruction.

Describe the solution you'd like
Instead of fetching each recipe on click in the recipe list view, one could retrieve all data in the first request when generating the recipes, together with not fetching AGAIN when pressing back from a recipe instruction.

Change gson usage in most api-calls and add more data classes.

Describe the bug
It is not possible to register a new user.

To Reproduce
Steps to reproduce the behavior:

1. Go to Login Activity Screen
2. Try to register a new user.

Expected behavior
Register a new user with an empty inventory etc.

Is your feature request related to a problem? Please describe.
Handling secrets in this application is not handled well, since a simple decompilation of the app will reveal them.

Describe the solution you'd like
Implement an Android Keystore.

Describe the bug
The title in the header is not Scanner when in the Scanner-view.

To Reproduce
Steps to reproduce the behavior:

1. Go to to any view in the bottom navigation bar.
2. Click on Scanner in the bottom navigation bar.
3. Title is wrong.

Expected behavior
Should be Scanner as title

Connect application to spoonacular API retrieving possible recipes.