This is an app I made as the final project for the Udacity course Android Basics: Data Storage.

The course taught the basics of database operations in Android using a SQLite database. From there, the instructors transitioned us to using Loaders and ContentResolvers instead of direct database operations, for better UI responsiveness and inter-operability between other apps.

The final assignment was to build an app that maintains and displays a list of inventory for an imaginary business.

I wanted to build an app that I could actually use myself; instead of a business inventory, this app maintains an inventory of the stuff that I have in the fridge/pantry. I have a bad habit of going shopping without checking beforehand what I have, so I end up with duplicates of a lot of stuff (especially spices - I have an absurd amount of cumin!).

It turned out pretty well for a first run. I'm especially pleased with the conversion functionality - the user can change the units displayed and the app converts to different units. In addition, when you mark some of the food as used, you can specify the units and the app does the correct calculation for you.

Some of the concepts that I had to learn on my own for this were:

• Camera intents and stored files
• Enabling/disabling UI elements
• Figma

I wanted to add the ability to take photos of the items. Using a camera intent was very easy, and I had never used a onActivityResult callback before, so that was valuable to learn. I also had to deal with loading the image in the correct orientation, which I did via a standard approach using the EXIF data and a Matrix object for the transform. However, I did this on the UI thread (I know, bad) so I'll need to fix this using a loader in a future commit so it's a little more peppy.

In the MainActivity there's an option to delete all the entries. I wanted to make one of those confirmation dialogs that make you type the word "delete" before allowing you to take such a drastic action. I implemented a TextWatcher to monitor the text box for changes and only enable the "delete" button if the user had typed the word delete.

I also toyed with disabling/enabling EditTexts in the EditorActivity, as originally I tried to have that activity serve both view and editing functions. This was a little more cumbersome than a button, but I was able to make it work. However, I scrapped it when I decided to polish the view UI a bit more and the dual purpose editor was no longer needed.

I built the mocks for the FoodViewActivity in Figma, an online mock-up creator that is awesome! I had never used a UI design app before and I was very pleased. It is so much easier and faster to try stuff out and build an outline in Figma than doing it in code in Android Studio initially.

• Use loader for images
• Add recipes