Android Clean Architecture

Implementing the Bookmark Project use case

This lesson is for PRO members.

Upgrade today to get access to all the PRO lessons.

Unlock this lesson

Autoplay

Up next

Implementing the UnBookmark Project use case (Domain layer 8)

Previous

Implementing the get Bookmarked Projects use case

About

Within Clean Architecture, the Domain layer defines Use Cases which define operations which can be performed in our application. In this lesson, we’ll be implementing the Bookmark Project Use Cases class for our application so that we can bookmark a project within our external data source through our domain layer.

Instructor

Links

Comments

This lesson should be before "Implementing the get Bookmarked Projects use case".

Can you explains why you're building a companion object in the Params class?

Sure thing! Because the use case classes are used within our view models, we need a way to kick off the work performed by the use case with some parameters. The Params class allows us to keep our buildUseCase() functions abstract (they need to be as all of our classes extend from the base use case classes). The reason for it being in a companion object is so that we can call the parameters function that we define within it - this way in future we can easily have multiple parameter functions incase we want to change the different parameters that are passed into the use case class. This keeps the constructor of the Params class private and enforces the parameters that can be passed into the class using these functions.

In a project where analytics is a requirement, for instance, I want to track how many users bookmark repos. Would you recommend including the analytics tracking in your use cases? Could please share from experiences in your projects?

>

You need to go PRO to post comments.

Log In or Go Pro

Lessons in Android Clean Architecture

Introduction to Clean Architecture

Android and Clean Architecture

Setting up a Multi-Module project

Setting up the Domain layer module

Creating the abstraction for our RxJava Observation Thread

Setting up the Business Data for the Domain Layer

Setting up the data access interface for the Domain Layer

Setting up the Domain Layer Interactor classes

Implementing the Get Projects use case

Implementing the get Bookmarked Projects use case

Implementing the Bookmark Project use case

Implementing the UnBookmark Project use case (Domain layer 8)

Testing the Get Projects use case

Testing the Get Bookmarked Projects use case

Testing the Bookmark Project use case

Testing the UnBookmark Project use case

Setting up the data module

Creating the data models for the data layer

Creating the external source interfaces for our data layer

Creating the data layer store interface

Creating the data layer cache data store

Creating the data layer remote data store

Creating the data store factory class

Creating the central access point for the data layer

Setting up the tests for the Data Layer

Testing the data store factory class

Testing the project entity mapper

Testing the projects data repository

Testing the projects cache data store

Testing the projects remote data store

Setting up the remote module

Creating the data models for the remote layer

Creating the Retrofit Service for the remote data source

Creating the Retrofit Service Factory for the remote service interface

Creating the data model mapper for the Remote Layer

Creating the Remote Source implementation

Setting up the Remote layer for testing

Testing the remote model mapper class

Testing the remote source implementation

Setting up the Cache module

Setting up the Cache layer data models

Creating the database for the cache layer

Creating the cached project Data Access Object

Creating the Configuration Data Access Object

Creating the cache model mapper

Creating the Projects Cache data source Implementation

Setting up the tests for our cache layer

Testing the cached project model mapper

Testing the Cached project DAO

Testing the Configuration DAO

Testing the projects cache implementation

Setting up the presentation module

Creating the data models for the presentation layer

Creating the data model mapper for the presentation layer

Creating the presentation state model

Creating the browse projects view model

Creating the bookmarked projects view model

Setting up the presentation module tests

Testing the view model mapper

Testing our Browse Projects View Model implementation

Testing our Browse Bookmarked Projects View Model implementation

Setting up the UI module

Creating the Post Execution Thread Implementation

Setting up the application class

Setting up the Dependency Injection for the UI module

Creating the UI modules Project representation

Creating the the Project model mapper for the UI module

Setting up the Browse Projects Activity

Configuring the DI for the project

Creating the Project item view

Creating the Browse Projects Adapter

Creating the browse bookmarked projects adapter

Creating the browse bookmarked projects activity

Tying together the browse projects and bookmarked projects activity

Setting up Unit Tests for the UI module

Test the project model mapper

Configuring the Dependency Injection for our User Interface tests

Writing Espresso tests for the Browse Projects Activity

Writing Espresso tests for the Bookmarked Projects Activity

Simplifying the work we have done