This was done in last year's app but not merged, so you can borrow the logic here

Ths was removed since the API didn't have any data. We should re-add it and add API implementation.

Some data logic is in the presentation layer. We should Remove them and clean them up.

Describe the bug
Some of the text in the about screen is not visible in dark theme mode

To Reproduce
Steps to reproduce the behavior:

1. Change device settings to dark theme before opening the app
2. Go to 'About'
3. See unreadable sections in screen

Expected behavior
Readable text

Screenshots
Added screenshot

With the new build plugins approach, we already have most stuff set up eg target SDK, and don't need to set them again in the Gradle files. Look for all the things that can be cleaned up

Ideally, the session card on the home page should show an image. You can compare it with the image when you open Sessions on the bottom navigation and open any session.

Check the screenshot below.

Finalize on Chai Design System for the app. Add:

• Texts
• Buttons
• Colors
• Cards

The project has the Bottom Sheet code from AOSP Project since at the time M3 didn't have the BottomSheet components but now the M3 supports the BottoSheets, this issue is to migrate to use these components and cleanup of the code in the bottomsheet package from AOSP.

Article here: https://www.composables.co/blog/bottomsheet

The filter session logic was using SQLBuilder logic which is commented out cause it was causing build issues. Change the implementation to use the Koltin approach.

If you change the device theme to dark mode and open the home screen the link to view all speakers and sessions doesn't match the designs.

Update documentation to remove references of droidcon 22 -> droidcon23

A clear and concise description of what the bug is.
The feedback emojis show the same feeling for Okay, Great, and Bad.

Expected behavior
Show different feelings for satisfaction.

Screenshots
EXPECTED

ACTUAL

We want to cache data to enhance performance for all the necessary network calls.

Start intents to share feed to:

• Twitter,
• WhatsApp
• Facebook
• Telegram

Describe the bug

Currently, most network/database operations in the repository layer are implemented in the main/UI thread. This might lead to ANR issues due to congestion in the main thread.

To Reproduce

N/A

Expected behavior

All network/database operations should run in the background/IO thread so as to minimize ANR issues.

When one is on the home screen and clicks on the Speakers card, there is a crash with the following message;

 java.lang.IllegalArgumentException: Navigation destination that matches request NavDeepLinkRequest{ uri=android-app://androidx.navigation//speaker_details/{speakerId} } cannot be found in the navigation graph NavGraph(0x0) startDestination={Destination(0x9f0a1621) route=/home}
                                                                                                    	at androidx.navigation.NavController.navigate(NavController.kt:1664)
                                                                                                    	at androidx.navigation.NavController.navigate(NavController.kt:1984)
                                                                                                    	at androidx.navigation.NavController.navigate$default(NavController.kt:1979)
                                                                                                    	at com.android254.presentation.common.navigation.NavigationKt$Navigation$2$1$2.invoke(Navigation.kt:45)
                                                                                                    	at com.android254.presentation.common.navigation.NavigationKt$Navigation$2$1$2.invoke(Navigation.kt:42)

If you open the Sessions destination in the bottom navigation and bookmark one session, it hides all the other sessions. This shouldn't be the case.

Current UI Tests Cover only display/exist assertions. We should add more tests to cover:

• States
• Whole app flow
• Screenshot testing??

When you switch to dark mode launch app and open Feed bottom navigation destination, the text is not visible. The dark mode designs can be found here

Apply the convention plugins using a version catalog instead of a string plugin ID which can be error-prone. A version catalog also helps in the discoverability of the available plugins.

I don't know if it's my configurations, but I've noticed that builds and syncs are a bit longer.

Is your feature request related to a problem? Please describe.
When the wrapper is updated by external contributors, there's the possibility of embedding malicious code in the .jar file.

Describe the solution you'd like
Gradle provides a GitHub action that checks if the wrapper matches one of their published SHA-256 checksums. If any file does not match, the action will fail.

Describe alternatives you've considered
Manually checking the checksum of gradle-wrapper.jar and validating if it matches any of Gradle's checksums.

Additional context
https://blog.gradle.org/gradle-wrapper-checksum-verification-github-action

I would like to contribute to the app but don't know where to start as there is no list of features pending for implementation.

Currently on the activity and HomeScreen we have @RequiresApi(Build.VERSION_CODES.O) we need to remove this

Describe the bug
The title text in the speaker screen is not visible in dark theme mode

To Reproduce
Steps to reproduce the behavior:

See unreadable sections in screen

1. Change device settings to dark theme before opening the app
2. Go to 'Speakers'
3. See unclear title

Expected behavior
Clear title

Screenshots
Added screenshot

Why?

Automate the release process of the app to the play store once all the tests pass.

How?

• Confirm/Setup configurations on Fastlane
• Test initial release for the beta/alpha version
• Publish the app to production

Currently, if you clone the project without having Java 11 setup, you'll face gradle errors. Update the readme with these instructions

If you navigate to the AboutScreen and scroll to the organizing team you'll notice the items are not spaced properly.

Speaker Image, on Home screen and when you view all speakers, has a teal background. This shouldn't be the case.

Currently, the app uses both StateFlow(check SpeakersViewModel ) and LiveData(Check SessionsViewModel) to hold UI data.

LiveData is officially deprecated, Check this reddit

Solution: migrate current implementations to use Stateflow and take advantage of the features of Kotlin Flows

Currently, we are using Android Gradle Plugin Version 7.4.1 we'd like to update to the latest version. Please test thoroughly that the app works after the update.

We are facing this crash on production with the below stacktrace.

Fatal Exception: android.database.sqlite.SQLiteException: near "1": syntax error (code 1 SQLITE_ERROR): , while compiling: 1
       at android.database.sqlite.SQLiteConnection.nativePrepareStatement(SQLiteConnection.java)
       at android.database.sqlite.SQLiteConnection.acquirePreparedStatement(SQLiteConnection.java:1055)
       at android.database.sqlite.SQLiteConnection.prepare(SQLiteConnection.java:662)
       at android.database.sqlite.SQLiteSession.prepare(SQLiteSession.java:590)
       at android.database.sqlite.SQLiteProgram.<init>(SQLiteProgram.java:61)
       at android.database.sqlite.SQLiteQuery.<init>(SQLiteQuery.java:37)
       at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:46)
       at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1556)
       at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1524)
       at androidx.sqlite.db.framework.FrameworkSQLiteDatabase.query(FrameworkSQLiteDatabase.kt:156)
       at androidx.room.RoomDatabase.query(RoomDatabase.kt:481)
       at androidx.room.util.DBUtil.query(DBUtil.kt:75)
       at com.android254.data.dao.SessionDao_Impl.fetchSessionsWithFilters(SessionDao_Impl.java:709)
       at com.android254.data.repos.SessionsManager$fetchAndSaveSessions$2.invokeSuspend(SessionsManager.kt:50)
       at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
       at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
       at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)
       at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
       at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
       at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
       at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
       at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)

1.Text color doesn't change when selected in bottom Nav
2.Text color not clear on dark mode in sessions screen

Describe the bug
In the presentation Module, one can't see a preview of the Feed screen in the IDE

To Reproduce
Refer to the screenshot below.

Expected behavior
A preview of the feed screen in the IDE

Screenshots

There are some screens like the SpeakersScreen where the speakers state variable is in the composable,i.e

val speakers = remember { mutableStateListOf<SpeakerUI>() }
LaunchedEffect(Unit) {
       speakers.addAll(speakersViewModel.getSpeakers())
 } 

then the speakers are loaded into the state using the LaunchedEffect block. I was suggesting if we could migrate the state from the composable to the view model and load it from there. Same thing with the SpeakerDetailsScreens and others

Based on the design of the FeedbackScreen, we want to have a collapsible top app bar.

Describe the bug
Some of the text in the feed screen is not visible in dark theme mode

To Reproduce
Steps to reproduce the behavior:

1. Change device settings to dark theme before opening the app
2. Go to 'Feed'
3. See unreadable sections in screen

Expected behavior
Readable text

Screenshots
Added screenshot

Currently, the test logic is commented out. We should fix this

Currently, the app uses collectAsState() API to collect flows in the UI.

collectAsState() is platform agnostic. So it's not aware of the Android lifecycle. This way it may keep the collection of the flows active even when the app is in the background wasting resources.

collectAsStateWithLifeCycle collects flows in a lifecycle-aware manner. It stops collecting flows when lifecycle moves out of the target state.
Find out more on consuming flows safely in jetpack compose here

Create more Convention Plugins eg:

• Compose
• Other Modules Needed

Refactor the codebase to use buttons in the Design System(Chai). Buttons are currently present in;

1. https://xd.adobe.com/view/dd5d0245-b92b-4678-9d4a-48b3a6f48191-880e/screen/1ef2f9cd-d83b-4618-8f29-655f3a9483ae/
2. https://xd.adobe.com/view/dd5d0245-b92b-4678-9d4a-48b3a6f48191-880e/screen/09ac0874-4933-4982-9e2e-b5d2c82d6c5f/
3. https://xd.adobe.com/view/dd5d0245-b92b-4678-9d4a-48b3a6f48191-880e/screen/8eef15fe-3d82-4c60-b9a1-f0b436119f7a/

When you are on the HomeScreen and Click on a session does not navigate to the session details screen.

Since Bottom Sheets are not yet in MD3, we have the AOSP code for the bottom sheets but the scrim color needs to be fixed. Check Share Feed & Filter Screens

EventDate uses LocalDate that uses Build.VERSION_CODES.O, which forces all files using this class to have a @RequiresApi(Build.VERSION_CODES.O) annotation. We should find a format that doesn't need this

Is your feature request related to a problem? Please describe.
We need to have a proper architecture documentation that:

• Shows what the app will look like and features it plugs into.
• Lack of this documented vision and direction often causes confusion to the contributors.

Describe the solution you'd like

• Create documentation before we start implementing features. Tools like Mockla or draw.io and a link to the diagram made open then linked to a docs section in the app.
• Require documentation of features as they are developed(Inline + or - on the markdown.

Describe alternatives you've considered
No documentation is the alternative and its a painful experience.

Additional context
Previous calls for documentation have been ignored an explanation by code owners would be great. See this issue