• [#117-1] Clear back stack after successful login/signup (Issue: When back navigation is pressed from Notes Screen, it tries to go back for sign in). [Fixed by #135]
• [#117-2] Add transitions while navigating among different screens (As present in simple app module).
• [#117-3] Add About screen for details regarding app (As present in simple app module). [Fixed by #135]
• [#117-4] Validate text fields before performing actions with ViewModel. [Fixed by #135]
• [#117-5] Create re-usable Composable components to reduce repetitive code.

Add transitions while navigating among different screens (As present in simple app module)

Currently, on the main screen (notes list), we have a menu which has "About". But it does nothing on click of the menu. Need to add AboutFragment which will have App details.

About screen can contain details as below:

• App logo
• App name
• App version
• GitHub URL

Implement major concepts used in Jetpack compose.

It will be useful if saved notes images will be visible in Gallery.

If the internet is unavailable, then save notes data locally and when connectivity is back then process the changes.

For e.g.

When the note is updated and if the internet is off then save change locally and process this change on the network once internet connectivity is back.

When user logs out (being in dark mode), the welcome back login prompt page has half white and half black background.
Also on back pressed, app didn't shutdown, instead same activity is recreated.

• Use SwipeRefreshLayout in NotesFragment for refreshing notes on demand.
• We can also look on a case where notes should get automatically refreshed when the note is deleted/updated or new note is added.

Note content for sharing externally is grammatically wrong currently. Need to fix this.

Preview

Currently, we don't have an optimized size of the application since we didn't shrink resources neither enabled proguard. It'll be good to have ProGuard enabled.

• Simple transition animations
• Transitions using MotionLayout.

Currently, we can share a note as text to external media. The feature request is to add a submenu where we will also be able to share a note as Image.

• After launching the main notes screen after logging/signing up, the screen is continuously flickering.
• This is happening in Compose application
• Suspected that it's happening with compose navigation lib:2.4.0-alpha05

Dagger not installed properly, getting error

• What went wrong:
  Execution failed for task ':kaptGenerateStubsKotlin'.

Could not resolve all files for configuration ':kapt'.
Could not resolve com.google.devtools.ksp:symbol-processing-api:1.5.20-1.0.0-beta03.
Required by:
project : > com.google.dagger:dagger-compiler:2.38.1 > com.google.dagger:dagger-spi:2.38.1
> Could not resolve com.google.devtools.ksp:symbol-processing-api:1.5.20-1.0.0-beta03.
> Could not get resource 'https://kotlin.bintray.com/ktor/com/google/devtools/ksp/symbol-processing-api/1.5.20-1.0.0-beta03/symbol-processing-api-1.5.20-1.0.0-beta03.pom'.
> Could not GET 'https://kotlin.bintray.com/ktor/com/google/devtools/ksp/symbol-processing-api/1.5.20-1.0.0-beta03/symbol-processing-api-1.5.20-1.0.0-beta03.pom'. Received status code 403 from server: Forbidden

And below my build.gradle

buildscript {
    repositories {
        jcenter()
    }
    
    dependencies {
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
    }
}

apply plugin: 'kotlin'
apply plugin: 'kotlin-kapt'
apply plugin: 'application'

group 'com.learn_ktor'
version '0.0.1'
mainClassName = "io.ktor.server.netty.EngineMain"

sourceSets {
    main.kotlin.srcDirs = main.java.srcDirs = ['src']
    test.kotlin.srcDirs = test.java.srcDirs = ['test']
    main.resources.srcDirs = ['resources']
    test.resources.srcDirs = ['testresources']
}

repositories {
    mavenLocal()
    jcenter()
    maven { url 'https://kotlin.bintray.com/ktor' }
}

dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk8:$kotlin_version"
    implementation "io.ktor:ktor-server-netty:$ktor_version"
    implementation "ch.qos.logback:logback-classic:$logback_version"
    implementation "io.ktor:ktor-server-core:$ktor_version"
    implementation "io.ktor:ktor-locations:$ktor_version"
    implementation "io.ktor:ktor-server-host-common:$ktor_version"
    implementation "io.ktor:ktor-auth:$ktor_version"
    implementation "io.ktor:ktor-auth-jwt:$ktor_version"
    implementation "io.ktor:ktor-gson:$ktor_version"
    testImplementation "io.ktor:ktor-server-tests:$ktor_version"

    // Exposed
    implementation "org.jetbrains.exposed:exposed-core:$exposed_version"
    implementation "org.jetbrains.exposed:exposed-dao:$exposed_version"
    implementation "org.jetbrains.exposed:exposed-jdbc:$exposed_version"
    implementation "org.jetbrains.exposed:exposed-jodatime:$exposed_version"

    // PostgreSQL
    implementation "org.postgresql:postgresql:$postgres_version"

    // Dagger
    implementation "com.google.dagger:dagger:$dagger_version"
    kapt "com.google.dagger:dagger-compiler:$dagger_version"
}

ktor_version=1.6.3
kotlin.code.style=official
kotlin_version=1.5.21
logback_version=1.2.5


exposed_version=0.33.1
hikari_version = 4.0.3
postgres_version=42.2.23.jre7
dagger_version = 2.38.1

• Refactor code for simpleapp.
• Remove code smells
• Reduce memory leakages from code.

• When tags are pushed, CI workflow should be triggered, APK should be generated.
• Generated APK should be automatically attached as a release artifact.

Here, room database is provided through dagger hilt as a singleton in the Application component, so I think it is not required to have the singleton pattern as hilt would ensure that room database instance is a singleton.

So it would be better to build the database in DatabaseModule itself.

    @Singleton
    @Provides
    fun provideDatabase(
        @ApplicationContext context: Context
    ) = Room.databaseBuilder(
        context.applicationContext,
        NotyDatabase::class.java,
        DB_NAME
    ).addMigrations(*DatabaseMigrations.MIGRATIONS).build()

As it is in simple app

• Add documentation for info about the project/repository.
• Add documentation for setting up the project locally.

Documentation Site (TBD)

This is a proposed idea for setting up a documentation site for this project where everything used in the project should be explained in the detail.
We can use docsify to set it up.

• Use custom dialog for showing loading/progress instead of ProgressBar.
• Use custom dialog for showing errors instead of Toast.

Username field should only take single-line inputs. Currently, it's accepting multi-line inputs.

• Create a new demo module for Jetpack Compose's implementation.
• Implement major concepts used in Jetpack compose.

• Setup CodeCov tool for measuring code coverage of the Noty Android application and API service.
• Not important at all. Still, we can consider this at then end.
• Currently blocked due to #15

In the notes details screen, share as Image option should be provided.

Question:
How to convert Composables into Bitmap?

we can use makrwon for this.

When the application's process is dead, use SavedStateHandle in ViewModel to recover data.

• Finalize UI for Android application.
• Implement good looking UI in the application.

Currently, in note add/detail fragment, EditText for note is not looking good to write long content. It's not responsive as it has to be. If it has the ability to scroll or smoothness then it would be nice.

While creating an account the password minimum requirements are not defined like the minimum length.

After creating an account if I click the back button, It navigates me to log in.

Cursor is showing if I share note as Image

It will be great to having an confirmation before deleting the note.

The motive behind this change is currently when tags are pushed then debug APK is generated and uploaded as a release artifact. We have also implemented LeakCanary library for debug mode. So app users are getting unnecessary notifications of LeakCanary which is bad experience :(. To avoid this, we should update release Actions workflow to upload only release APK which won't include LeakCanary.

In notes screen, pull to refresh/swipe refresh composable is necessary to sync remote notes with local notes. Refer simple app for the story.

In compose app variant, UI for input fields is not looking good and not in sync with the simple app as well. Make input fields of title and note body simple instead of using material component

Hello, when i add a note, i'm redirected to the main notes fragment, and when i click on the Add FAB, the app navigate to the AddNoteFragment and instantly navigate back to the NotesFragment, because in the AddNoteViewModel, the viewState variable is not reset when a new note is created and if we navigate in AddNoteFragment it will re-observe the Success state of the viewState and navigate back

Increase default width of title and description. So it can be clickable from right hand side also.

To reduce network traffic, we should not enable SAVE button unless there's an actual change in a note.

• If we change DarkMode->LightMode or vice versa, notes are re-synced.
• Also happening on device orientation change

• Add Unit tests for modules data, repository, app etc.
• Add some integrations tests for Android.
• We can use libraries like Kotest, Mockk, etc for testing which are completely Kotlin libraries.

Shadow is cutting from bottom in Visit card

Use StateFlow/SharedFlow instead of LiveData in ViewModels

None of this is really necessary but I enjoyed doing it :)

Submitting PR

Thanks!

-Alexi

Add code documentation for classes, methods and fields (if required)

• Show error dialog in Sign In/Sign up fragments
• Show small info in Notes fragment
• Show error when tried to add/update/delete note.