Okay so currently the flow I have is like this:

• Go to the websites where I like to watch animu
• Go back to the app and press +1

There are few problems with that, the one I wish to solve right now is ability to add links to the items on home page, so instead of memorizing the websites, I could just save them inside the app.

For example, on the bottom sheet there could be a new Button named "add link", this button would open a new dialog with EditText, where user will paste the link. Then on the home page next to +1 a new button will show up and pressing it will open the website

Bottom Sheet	Home Page

Currently the auth token is stored from within the Auth module, it might be cleaner to extract this out into its own module.

The avatar is currently set from the Activity, it would be nice if it was its own Fragment that gets included and put into the navigation drawer.
Could be its own module that gets pulled into the app module.

Create a widget to use with the application. It should be able to talk to the account module to get and send information.

Currently detekt only looks at the src/main/java directory, it should be changed to look at src/ instead, and all of the issues that have risen up in tests should be fixed, or the config updated to ignore those issues.

When the application force logs a user out due to an invalid auth/refresh token it just kicks them back to the login screen, with no information. A snackbar or notification or something should appear to notify the user that they were logged out.

In the KitsuLibrary reflection is used to call suspending functions, it could be removed to not need to use reflection.

This is the sole recorder of literature and videography that I have located available via F-Droid. Consequently, although I would be very pleased if this were to become able to record more generic information – not solely Japanese.

Consequently, all that I shall propose is management of alternate trackers of Japanese media, 2 of which are https://anilist.co and https://myanimelist.net. I utilize primarily https://anilist.co, so addition of that website would allow me to easily synchronize it with or transfer the data of it to https://kitsu.io (which I have estimated is probably your favourite).

I am thankful for any consideration.

The login flow currently has a white background, with the bar visible at the top of the screen. It would probably look better if the bar was made white to match the background, with black icons so they are still visible.

These would be visible only on the login module screens, then disappear once back on the main application screens.

In order to keep the "Core" module smaller, some of the classes could be extracted into their own modules, or put in other modules where it makes sense.

The LibraryAPI currently deals with all retrieval and management of the library, it could be split up so one API is used for retrieval of all the series (can also then deal with a singular series), and one for managing the API itself.

Have the developers considered getting this app included on F-Droid?

Given that Fastlane is already used here, all that's left is to submit metadata and wait for approval.

Please consider updating the interface to material you,
Material You allow for better UI consistency across devices, it makes them easier to use, and it adapts to user color scheme preferences.

Leak canary is throwing up some issues while interacting with the application, try to find fixes to them.
The main leak seems to be when navigating to the settings screen.

Currently Resource is used across the application for all API calls. This currently resides within the core module so changing it means recompiling everything.
An idea would be to change from using Resource to instead have a different sealed class per functional area. This means that using it would be a bit cleaner, and hold the correct data.

The Search library could for example return

sealed class SearchResult {
    data class Success(items: List<SearchDomain>): SearchResult
    object AuthFailure(): SearchResult
    object EmptyResultFailure(): SearchResult
    ...
}

Which means further down the chain we already have the result parsed out, and have no need to check the error code, instead we can check against the SearchResult.

Currently all requests that require and authenticated API report the failure down to the viewmodel, which then executes a log out of the application. It would be better if there was some global handler for this behaviour, since we always want to execute a log out when the refresh token is invalid.

Hilt is a new component of Dagger, it should replace dagger-android. https://developer.android.com/training/dependency-injection/hilt-android

Having the application sitting around unused for awhile (untested amount of time) looks like the auth token becomes invalid, and the refresh token also becomes invalid and doesn't update.
Need to investigate if the worker isn't running or if it isn't updating the auth token internally.

Instead of needing to spin an emulator up to run the tests, would be nicer to just run them using Robolectic.

Series currently refresh in the background, but there is no way to manually force a refresh. Could use pull to refresh, or a refresh button in the app bar.

Add a module that will show a users activity.
Can show it as a list of times initially (you watched x at y), but later on this should probably be a graph so its a bit easier to see how many shows were seen on which day etc.

Using the AboutLibraries plugin seems to make a lot of the libraries disappear from the licenses list, this is likely due to it being a multi-module project.
Need to find out how to fix this and use the new plugin instead of using the AboutLibraries definitions dependency.

Currently an error occurs and the user is forced to manually log out, we need to check the return code and if its a failure for invalid token we need to force the log out.
This occurs from within the series list.

Change the text from saying "????-??-??" to instead say "Ongoing", as it reads nicer to the user

Update to include screenshots for dark mode.

Some of the DTO contain fields that aren't being used, such as in the Auth module where only a couple of fields are stored or used. Some of this data could be removed to clean up the DTOs, this would also improve coverage in those areas since the unused code isn't tested.

For some reason I see "Attack on Titan" in my list. I usually have romaji titles displayed and would strongly prefer that here. It's a bit disorienting not having them, because I sort by title, and so things actually aren't where I expect this way. (A section vs S section in this case)

Add a module to show information about the user.
Information that would be displayed are minor stats such as the total series in each state, the total anime series, the total manga series, estimated time spent watching series etc. Some of this information can be pulled from the API.

Running the app on my tablet (Samsung Tab A 10.1), it looks like it never seems to update in the background, so the auth token will eventually expire regardless.

This could be something to do with the worker that starts up not being in the foreground so it gets killed before it can execute. Or it could be that the service is just never started up again.

Either way need to investigate into this.

The account manager would be cool to play around with, so see if it can be integrated in.

It looks like the code coverage across the modules isn't being reported correctly, since the UI tests are all in the app module it looks like it isn't working for coverage across the fragments in other modules.

Might need to have custom jacoco settings for each module, which reflect that the tests are in the app layer?

Add an option into settings that allows the user to choose their default starting screen. Currently it defaults to "Anime", but some users may only use the app to track their manga usage so it would be nice to allow them to default to Manga.

I only have manga added to my library, on the first login it was able to successfully sync the data, but after I tried updating an entry on the website and refreshed the list on the app, it failed to sync the contents.

I was able to successfully refresh the list if at least one anime entry was in my library, otherwise the sync fails.
So I'm assuming that the code assumes both the lists must have some entries.
Hope it gets fixed, Thanks for the app.

There should be some sort of way to navigate straight to search from the series list, to make it a bit easier to show how new series can be tracked. This could be a FAB on the series list itself that links into the search flow.

I would like to translate Nekome into Japanese. Does Nekome support the translation?

Is it possible to add support to other services like MyAnimeList?

I would like a darker dark theme, both for aesthetic reasons and because it saves battery life on most modern phone screens. It could be a separate theme choice or a checkbox to change the dark theme's look. I have seen it both ways in other apps.

Instead of just saying "Results" on the results page, it should instead have the text that was searched for

The subtitle for the avatar view is currently hardcoded to Kitsu. Find something more interesting to map it to. Maybe number of series tracked or something.

Change from using a UserModel to store in the database and move around the application, instead convert to a UserEntity to store in the database, then convert to something such as a UserDomain for use in the application.

If activity recreation occurs while sitting on the login details screen, then the user will be taken to the anime/manga list without being logged in.
The reason for this is likely that when the activity is recreated

        if (savedInstanceState == null && !viewModel.userLoggedIn) {

is used in the onCreate which on recreation is skipped because savedInstanceState is not null so the nav graph goes straight to the anime/manga list.
Should be a case of making sure it doesn't default to anime/manga and instead doing it manually.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency fastlane to v2.220.0
• chore(deps): update dependency gradle to v8.7
• fix(deps): update dependency androidx.browser:browser to v1.8.0
• fix(deps): update dependency androidx.core:core-ktx to v1.13.1
• fix(deps): update dependency androidx.datastore:datastore-preferences to v1.1.1
• fix(deps): update dependency androidx.fragment:fragment-ktx to v1.7.0
• fix(deps): update dependency com.google.android.material:material to v1.12.0
• fix(deps): update dependency com.squareup.leakcanary:leakcanary-android to v2.14
• fix(deps): update dependency org.robolectric:robolectric to v4.12.1
• fix(deps): update retrofit to v2.11.0 (com.squareup.retrofit2:converter-moshi, com.squareup.retrofit2:retrofit)
• fix(deps): update dependency com.michael-bull.kotlin-result:kotlin-result to v2
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency org.jetbrains.kotlin.android to v1.9.24
• chore(deps): update detekt to v1.23.6 (io.gitlab.arturbosch.detekt, io.gitlab.arturbosch.detekt:detekt-formatting)
• chore(deps): update plugin google-devtools-ksp to v1.9.24-1.0.20
• fix(deps): update dependency androidx.compose.material3:material3 to v1.2.1
• fix(deps): update dependency io.nlopez.compose.rules:detekt to v0.3.20
• fix(deps): update kotlin.coroutines to v1.8.1 (org.jetbrains.kotlinx:kotlinx-coroutines-test, org.jetbrains.kotlinx:kotlinx-coroutines-core, org.jetbrains.kotlinx:kotlinx-coroutines-android)
• chore(deps): update android.gradle.plugin to v8.4.0 (com.android.library, com.android.application)
• fix(deps): update dependency androidx.compose:compose-bom to v2024.05.00
• chore(deps): update plugin ktlint to v12
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Currently pressing sort on the series list shows a list of possible sort options. It would be nicer if more options could be added and with an ascending/descending option.
This could pop up as a bottom sheet instead of a dialog.

Based on what did you structure the modules? I also want to do similar way on my project and wanted to know what led you to the current state of feature and libraries structure...

I am trying to build a Jellyfin client, it will be something like Plex or Emby. There was other articles too, and many reddit posts, but I posted this question here because... there is a whole project as an example :D

So what was the pros and cons of this modular aproach you used?

Does it support anilist too or only Kitsu? Since it appeared in the advanced github search so idk

In various parts of the application Domain objects are converted into a SeriesModel which is used for display to the user, these instances should be changed to models specific to that view so its easier to change.

Add a new application module that will be used to show upcoming shows. Will need some UI to show the current day and what will be shown on the upcoming days, probably limited to the next 7 days, or next 4 weeks?

The login screens currently exist within the main app module, but they should sit in their own module named app-login.

Currently all the UI tests mock out the APIs to communicate with the server, it might be more beneficial to instead use a mock server, so the whole framework is tested against.