007 ArtBook Introduction

Creating an Art Book Application from Scratch

Overview of the Application

• The session focuses on building an art book application that allows users to save and manage images of paintings they love.

• Users can take photos, save them in SQLite using Room, and later review or delete them as needed.

Key Features and Technologies

• The application will utilize Room for database management instead of raw SQL queries, enhancing data handling efficiency.

• A RecyclerView will be implemented to display saved images dynamically within the app. Additionally, Retrofit will be used to fetch images from an API rather than directly from the user's gallery or camera.

User Interaction Flow

• When a user clicks on a floating action button, they can search for images (e.g., "Mona Lisa" or "The Scream") through an interface that allows inputting details like artist name and year created.

• Users can add new entries with relevant information about each painting, including the option to delete existing ones if desired. This functionality is demonstrated with examples such as saving "The Scream" by Edward Munch.

Development Approach

• The development process will incorporate various components typical in real-life applications: Room database, dependency injection via Hilt, ViewModels, LiveData, Fragments, and Navigation components. This aims to create a professional-grade application structure following MVVM principles.

• Testing will also be integrated into the development workflow to ensure reliability and performance of the application features over time.

Learning Opportunities

• The instructor encourages both novice and experienced developers to follow along with the coding process for hands-on learning opportunities regarding new elements like view binding and navigation components that may not have been previously encountered by some learners.