Skip to content
Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Mobile App Development

Name: Rudine Surya Hartanto


Demo Video:

Table of Contents


App Concept

This is an app for quick contract job, similar to the likes of Meetup. It has some form of social networking feature, eg. the ability to view user's profile and chat


  • For the host: Enable quick solution for finding adhoc work done.
  • For the jobseeker: Enable checking out the job details and payment before joining.

Personal Statement

This App has taken some inspirations from meetup ( and airbnb ( This is also my first large scale android development project with many experimentation with new libraries and kotlin language.

Business Case

The usage of the App is not limited to employer only. Anyone can create a job such like a landlord can put his property for rent. The company could use a profit sharing business model, in exchange the user gain the platform. All the marketting and promoting will be done by the company.

Future Development and Possibilities

At the current state, due to lack of time, some of the implementation and design pattern were rushed. This makes automated testings and maintainence difficult. Also, I am storing duplicate data in Firestore for most of the document referencing. It can be improved further by either storing user doc reference (Not sure if it might double the query), or by having a cloud function which periodically aggregate the data to sync.

What can be done better

  • Better seperation of concern between Activity/Fragment and ViewModels.
  • Add delete functionality to the user and job model.
  • Add cleanup functionality to remove orphaned files the deleted user/job leaves behind.
  • Move certain part of the backend codes to the cloud. This gives a few advantages. More security at the data layer. Cleaner code at the client App. It also can be re-used by other App that uses the same backend, eg. IOS/Web.
  • Pagination for loading a large collection.

Installation Requirements

Must provide your own google-services.json with valid api key

Recommended version of android is Oreo


  • CRUD operation with cloud persistence (Firestore)
  • List Jobs (Sorting, Filtering)
  • Dynamic map view with gps (view nearby jobs and also places of interests)
  • View & Edit Job Detail (with authentication)
  • Chat system in the job page
  • Push notification sent to participants (when job cancelled/resumed)
  • Login / Register
  • View other user's profile
  • Edit self user profile
  • Join / Leave Job
  • Custom Notifications

UI Design

Clean Design Concept

  • Use action bar and navigation drawer to place menu items instead of cluttering them on the activity fragment.
  • Sensible navigation and deep linking.
  • For more important features, allow multiple way to access it besides a button. (nav drawer)
  • User can sign out from anywhere in the app. (nav drawer)
  • Async loading enables seamless and smooth experience for the user.
  • Show loading bars when possible.

Adherence to the Android Material Design

  • CoordinatorLayout extends the ability to accomplish many of the Google's Material Design scrolling effects.
  • parallax scrolling effects animations for the action bars during scrolling effect.
  • expanding and collapsing action bar allows more screen real estate for displaying more important stuffs.

Benefit of EpoxyRecyclerView from Airbnb

  • dynamic recyclerview made simpler. No need to deal with the hassle of defining multiple viewholders. In the above gif, the date headers are only generated when the date changes. This presents a pleasing ui for the end user.

  • recyclerview within recyclerview. In the above gif, the job detail page is created using epoxy recyclerview. Carousell is a child recyclerview inside of it.


Show error messages to user in the form and also show toast message when something significant happens (eg. new entry to db / error)


Uses Firebase Authentication to enable simple user registeration and logging in, and also enable google authentication.

Receiving Notifications

Uses cloud function event trigger to send notifications to devices.

  • Notifications can be sent to topic, where only subscribed users will receive.
  • Notifications can also be sent to specific tokens. This is used when the notification only concern certain group of users.

  • user can also choose to get or ignore certain notifications by going to the settings menu to opt.

Integration With Android Ecosystem

  • Static maps can launch an intent to open the user's Google Maps.
  • Clicking on the job date will prompt user if he/she wants to add the job detail to the Google Calendar.
  • Other usage of intent filter for sharing job to (gmail,facebook,whatsap, other social media)

Development Features


  • Using best practices for relationship database design
  • Usage of sub-collection within documents to optimize read
  • Usage of cross referencing with key ids to avoids multiple querying for specific results
  • Having a special class to cache common documents.

The store class is created to reduce calls to firestore for fetching the same data multiple times due to many screens sharing the same data. We reduced the number of calls from one call per activity/fragment to a single call throughout the whole app. There is no reason to constantly request for data as we are using listener and will receive live update from the database.

 * Class used to hold references to common objects to avoid multiple querying of the same data
class Store(private val repository: MyRepository) {
    // LiveData
    private val _jobs = MutableLiveData<List<Job>>()
    val jobs: LiveData<List<Job>?>
        get() = _jobs


    init {

    fun fetchAllJobs() {
        Timber.d("fetching All Jobs")
        repository.getAllJobsLiveData {
            it.observeForever {

MVVM Architecture Adopted

Architecture components help you structure your app in a way that is robust, testable, and maintainable with less boilerplate code.

This diagram shows a basic form of this architecture:


The view role in this pattern is to observe (or subscribe to) a ViewModel observable to get data in order to update UI elements accordingly.


ViewModel interacts with model and also prepares observable(s) that can be observed by a View. Acts as a communication center between the Repository and the UI. Hides where the data originates from the UI. ViewModel instances survive Activity/Fragment recreation.


Model represents the data and business logic of the app. One of the recommended implementation strategies of this layer, is to expose its data through observables to be decoupled completely from ViewModel or any other observer/consumer.

The following diagram shows MVVM components and basic interactions.


A data holder class that can be observed. The UI that is observing the livedata will react when data changes. This allows the components in your app to be able to observe LiveData objects for changes without creating explicit and rigid dependency paths between them. LiveData respects Android Lifecycle and will not invoke its observer callback unless the LiveData host (activity or fragment) is in an active state. Adding to this, LiveData will also automatically remove the observer when the its host receives onDestroy().


A Repository class abstracts access to multiple data sources.


Data access object. Interface between Repository and the database.


cloud persistence database which also supports caching for offline data.

Remote Data Source:

For making REST API requests to the web.

Advantages of MVVM with Clean Architecture

  • MVVM separates your view (i.e. Activities and Fragments) from your business logic.
  • Your code is further decoupled.
  • The package structure gets easier to navigate.
  • The project is easier to maintain.
  • Your team can add new features more quickly.

Git Approach Adopted

  • Nothing special as it is a one developer project.
  • Commits small improvements or bug fixes with useful comments to enable reverting back quickly when something goes wrong.
  • ignore unnecessary files from git

Complex Model Schema

User entity holds its own references to jobs that he/she has joined. This enables fast querying in the job dashboard, when we want to filter jobs that the current user has joined or has saved as favourite.

Job entity creates sub-collection to hold users that have joined and another collection for holding all the comments. This strategy can further be improved for large data as we can query sub-collection by pages. The advantage of not storing all these references in the job entity itself is that we dont bloat up the job entity size by irrelevant data. We also avoid hitting the size limit per document.



For cloud persistence of user and job entities


For local persistence of notification object


For settings preferences

Third Party Components

  • Latest Android Architecture and Support Libraries

    • android arch
    • android jetpack
    • android ktx
    • kotlin coroutines
    • Room
  • Logging Support

    • timber (for logging)
  • Firebase Support

    • Firestore
    • Firebase Authentication
    • Firebase Storage
    • FirestoreLiveData
  • UI Enhancement Components

    • google maps
    • places-autocomplete
    • glide
    • date-time-picker
    • epoxy recyclerview
    • spots-dialog
  • Code Enhancement Components

    • retrofit
    • kodein
    • junit4
    • espresso
    • mockk
    • assertj

Third Party Api

  • Google Maps
  • Google Places
  • Google Autocomplete
  • GPS
  • Firebase Firestore
  • Firebase Authentication
  • Firebase Messaging
  • Firebase cloud function

Google Maps, GPS, together with Google Places API are used for making REST requests with retrofit to get a list of nearby places of interest to display on the dynamic map view activity.

Firebase cloud function is used as event trigger for when a job gets cancelled or resumed by host. It will then notify all participants involved.

exports.notifyJobCancelled = functions.firestore
  .onUpdate((change, context) => {
    const after =;
    const jobId =;
    // Creates the notification payload
      .then(snapshot => {
        const notificationBody = after.status ? 'Host resumed the job' : 'Host cancelled the job';
        const payload = {
          notification: {
            title: 'FastJobs alert',
            body: notificationBody,
            clickAction: 'JobDetailActivity',

        // Send this notification to every registered tokens
        snapshot.forEach(user => {
          console.log(`userId ${}`)
            .then(user => {
              const token =
              admin.messaging().sendToDevice(token, payload);
            .catch(err => console.log(err));
      .catch(err => console.log(err));

Folder Structure

The code is divided into three separate layers:

Presentation Layer

This includes Activities, Fragments, RecyclerView Views. The sole responsibilities is to take user inputs and obtain data from the domain layer and display them to view. We can call async functions by using coroutine scope.

Domain Layer

This includes ViewModels. The domain layer contains all the use cases of the application. Codes in this layer are designed to look synchronous, but with asynchronous signature (to be called from the activity/fragment). Mediator between views and repository.

Data Layer

This includes Room's Database, Data Access Objects (Daos), restful api service, Repository and Models. The Repository is the single source of truth when it comes to accessing data from remote server or api services.

 * Single source of truth for database access
class MyRepository(
    private val userDao: UserDao,
    private val jobDao: JobDao,
    private val nearbyPlacesDataSource: NearbyPlacesDataSource
) {
    fun getUserById(id: String, onSuccess: (User?) -> Unit = {}) {
        userDao.getUserById(id, onSuccess)

    fun addJob(job: Job, onSuccess: () -> Unit = {}, onFailure: (Exception) -> Unit = {}) {
        jobDao.addJob(job, onSuccess, onFailure)

    fun fetchNearbyPlaces(
        location: String,
        radius: String,
        type: String,
        onSuccess: (NearbyPlacesResponse) -> Unit = {},
        onFailure: (Throwable) -> Unit = {}
    ) {
        nearbyPlacesDataSource.fetchNearbyPlaces(location, radius, type, onSuccess, onFailure)

Dependency Injection

Dependency injection is an instrumental technique, used to decouple dependencies from the code.

Make our application KodeinAware

To provide dependencies to other classes, we need to supply kodein all the dependencies, usually done in the Application class as there will only be one instance of that class and it does not have a lifecycle.

class MyApplication : Application(), KodeinAware {
    override val kodein = Kodein.lazy {

        bind() from singleton { FirebaseFirestore.getInstance() }
        bind() from singleton { JobDao(instance()) }
        bind() from singleton { MyRepository(instance(), instance(), instance(), instance()) }
        bind() from provider { ViewModelFactory(instance(), instance(), instance(), instance()) }

To enable the dependencies to be passed, we need our classes to implement KodeinAware interface. This gives us an advantage of maintaining clean code and reduce lots of boilerplate due to passing references between classes.

class JobListFragment : KodeinAware {
    override val kodein: Kodein by closestKodein()
    private val viewModelFactory: ViewModelFactory by instance() // Get access to the view model factory
    private val auth: Auth by instance() // Get access to the auth class


    override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
        super.onViewCreated(view, savedInstanceState)
        viewModel = ViewModelProviders.of(this, viewModelFactory)



Unit Tests

  • Testing of Model data classes

Instrumentation Tests

  • Testing of network rest api services
  • Testing of Data Access Object (DAO)



Job catalog app that runs on native android (MVVM, Retrofit, Kodein, Firebase, Maps)






No releases published


No packages published