Develop a consistent error-handling approach throughout the application, ensuring proper error messages are displayed to users.

By the end of the third week of June (〜6/23, 2023)

• [Design] Designing the Application-wide Aspects (Theme, Navigation, and Screen Structure)

By the end of June (〜6/30, 2023)

• Create Screen structure implementation

By the end of the first week of July (〜7/7, 2023)

• [Design] Design for essential features

〜7/23, 2023

• Stamps design

By the end of July (〜7/31, 2023)

• Create essential features

By the middle of August (〜8/13, 2023)

• Create issues for Contributors
• Adjust for publishing
• Stamps feature
• [Design] App Icon
• [Design] Create other screen designs

8/14, 2023

• Publish the application as OSS

9/14, 2023

• DroidKaigi 2023

Consider introducing Zipline experimentally on a single screen to evaluate its benefits and potential integration with the existing application architecture.
Consider ways to capitalize on Zipline for the creation of UI Models and its ability to enable immediate release.

make an empty session detail screen and navigation code.

https://github.com/iurysza/module-graph で Mermaid でgradle moduleの依存図を吐けるので、入れてみると便利そう。

LinterとしてDetektを検討してもいいのかも。(KtLintはフォーマッターとしてだけ使う)

ビルドエラーにしてPR書く人になおしていただく？（でも、コントリビュートが煩わしくなりそう）

PRへのコメント自体は下記が参考になりそう（detektでlintエラー検知したよ、ぐらいになるかもしれないけど）

https://github.com/DroidKaigi/conference-app-2023/pull/50/files

議事録該当部分：https://docs.google.com/document/d/1ubIgbJri12nxVcyBMuOR0qyNgbrdi6vqAp0Xvnvg_Zw/edit#bookmark=id.av4datq9b05k

• Find a package structure strategy through discussion
• Close the issue if we can't find any strategy until 5/5

Divide the application into layers based on their roles, such as Data Layer, Domain Layer, and Presentation Layer, to improve code reusability and maintainability.

Make compose lint run on Format of GitHub Actions.
https://github.com/DroidKaigi/conference-app-2023/blob/main/.github/workflows/Format.yml

I believe we need to create "feature/session" and "core/data" modules at least.

I would like to fix this 😢

Maybe we can fix it like this (From a Compose Theme of Android Studio Headgehog's New Project)

    SideEffect {
      val window = (view.context as Activity).window
      window.statusBarColor = colorScheme.primary.toArgb()
      WindowCompat.getInsetsController(window, view).isAppearanceLightStatusBars = darkTheme
    }

The current codebase don't use Gradle's cache system properly so some tasks like Lint are fully executed. The build time will be significantly decreased if we can properly use Gradle builds.

We may have to introduce a navigation library. like Compose Navigation

As the alpha version of Compose for iOS has been released, we are conducting research and considering the use of Compose Multiplatform for developing a conference app. It seems possible to partially adopt Compose for iOS by implementing screens that can be developed using it, so we plan to implement those screens with Compose for iOS and consider using Swift UI for more complex screens.

• Ready to develop the app using Compose Multiplatform
• Try preparing ourselves to be able to start creating screens right away

今の置き場所
https://github.com/DroidKaigi/conference-app-2023/tree/main/build-logic/src/main/kotlin/io/github/droidkaigi/confsched2023

Gradle Pluginを複数回applyしても再適用されない事を知らなかったので、
これを元にもっと使いやすくできないかな、と考えている。

NowInAndroidのfeature同士は依存してはダメでcore同士は依存OKのように、分け方を改善できないか。

例えば、ComposeのGradlePluginはAndroidのGardlePluginに依存して良いのでは無いか？
（使う側でComposeのGradlePluginの依存関係を意識しなくても、ComposeのGradlePluginを使うだけで必要なGradlePlugin達を全部applyしてくれる）

たぶん、問題はあるGradlePluginを使う時に、そのGardlePluginが何に依存しているかを知って、その依存先のGradlePluginを全部明示的に使う設定が必要、というところ。

revise KMM

For example, if we introduce https://github.com/EnricoMi/publish-unit-test-result-action, we can see the result of local unit tests like this:

• Add at Least One Light or Dark Theme
• Add Design System Module

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: packageRules[0]: packageRules cannot combine both matchUpdateTypes and versioning. Rule: {"groupName":"gh-actions","prPriority":-1,"matchManagers":["github-actions"],"matchUpdateTypes":["minor","patch"],"matchDatasources":["github-tags"],"versioning":"semver","automerge":true,"platformAutomerge":true,"pinDigests":true,"schedule":["after 10am before 5pm on tuesday"]}

参考：https://chris.banes.me/posts/slotting-in-with-compose-ui/
議事録：https://docs.google.com/document/d/1ubIgbJri12nxVcyBMuOR0qyNgbrdi6vqAp0Xvnvg_Zw/edit#bookmark=id.egny3h61hz2x

• Make a contributors module
• Make an example about 'Slot' API pattern in codebase
• Write down a description about 'Slot' API pattern in README

spotless自体のアップデートにこける事がある程度ある。
便利は便利なんだけど、必ずspotlessである必要性は薄い。

spotlessをアップデートして様子を見るか、同等の我々が使用している機能（コードフォーマットの逸脱検知＆コードフォーマットの実施）を他の方法で実現するかを考える。
素のktlintでも実は事足りる可能性がある。

We aim to test the app effectively. To achieve this, we need to determine what aspects to test and how to approach the app's implementation testing.

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

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• chore(deps): update marocchino/sticky-pull-request-comment digest to 8361604
• chore(deps): update kotlin monorepo to v1.8.21 (org.jetbrains.kotlin.android, org.jetbrains.kotlin:kotlin-gradle-plugin)
• fix(deps): update dependency com.diffplug.spotless:spotless-plugin-gradle to v6.18.0

Detected dependencies

Investigate how to realize Edge-to-edge using Jetpack Compose, Material Design 3.

• Clarify how to realize and points to note

We've already checked the code format of PRs by Format GitHub Action.
But the contributors may forget to format their own code before creating their PRs.
It would be better to introduce a way to avoid forgetting it.

example result:
https://github.com/DroidKaigi/conference-app-2023/pull/138/files

usage:

brew install shellcheck
brew install actionlint
actionlint .github/workflows/

The current structure is like core-ui.

refer
https://github.com/DroidKaigi/conference-app-2022
https://github.com/android/nowinandroid

Maybe DroidKaigi2023Theme is better 👀
https://github.com/DroidKaigi/conference-app-2023/blob/f8832b0838640fb17a26edd7f6fb286f0c3057d2/core/ui/src/main/java/io/github/droidkaigi/confsched2023/ui/theme/Theme.kt#LL31C1-L31C1

.catch {
    // ② Application wide error handling
    val applicationErrorMessage = it.toApplicationErrorMessage()

    // Shared snackbar message logic
    val messageResult = showMessage(
        message = applicationErrorMessage,
        // TODO: Decide how to write strings in ViewModel
        actionLabel = "Retry"
    )

    // Retry
    if (messageResult == UserMessageResult.ActionPerformed) {
        emitAll(sessionsRepository.getSessionsStream())
    }
}

I would like to make an extension function to centralize error-handling logic

We should change present "example" package name.

議事録該当部分：https://docs.google.com/document/d/1ubIgbJri12nxVcyBMuOR0qyNgbrdi6vqAp0Xvnvg_Zw/edit#bookmark=id.5oogn4tmynvt

• Judge if the feature would need something related on foundation layer
• Introduce them if needed

The title says everything

Select an appropriate design pattern for the application, such as Guide to app architecture based architecture, Redux, MVI...

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.

• Update actions/cache digest to e12d46a
• Update peter-evans/create-or-update-comment digest to 23ff157
• Update dependency androidx.activity:activity-compose to v1.8.2
• Update dependency androidx.fragment:fragment to v1.6.2
• Update dependency androidx.navigation:navigation-compose to v2.7.7
• Update dependency co.touchlab:kermit to v1.2.3
• Update dependency com.android.tools:desugar_jdk_libs to v2.0.4
• Update dependency org.jetbrains.kotlinx:kotlinx-collections-immutable to v0.3.7
• Update dependency org.jetbrains.kotlinx:kotlinx-serialization-json to v1.6.3
• Update detekt to v1.23.5 (io.gitlab.arturbosch.detekt, io.gitlab.arturbosch.detekt:detekt-formatting, io.gitlab.arturbosch.detekt:detekt-gradle-plugin)
• Update kover to v0.7.6 (org.jetbrains.kotlinx.kover, org.jetbrains.kotlinx:kover-gradle-plugin)
• Update ksp to v1.9.23-1.0.19 (com.google.devtools.ksp, com.google.devtools.ksp:com.google.devtools.ksp.gradle.plugin)
• Update ktor to v2.3.9 (io.ktor:ktor-client-content-negotiation, io.ktor:ktor-serialization-kotlinx-json, io.ktor:ktor-client-darwin, io.ktor:ktor-client-okhttp, io.ktor:ktor-client-core)
• Update androidGradlePlugin to v8.3.1 (com.android.library, com.android.application, com.android.tools.build:gradle)
• Update dagger to v2.51 (com.google.dagger.hilt.android, com.google.dagger:hilt-android-compiler, com.google.dagger:hilt-android-testing, com.google.dagger:hilt-android, com.google.dagger:hilt-android-gradle-plugin)
• Update dependency androidx.browser:browser to v1.8.0
• Update dependency androidx.compose.animation:animation-graphics-android to v1.6.4
• Update dependency androidx.compose:compose-bom to v2023.10.01
• Update dependency androidx.hilt:hilt-navigation-compose to v1.2.0
• Update dependency androidx.lifecycle:lifecycle-process to v2.7.0
• Update dependency androidx.lifecycle:lifecycle-runtime-ktx to v2.7.0
• Update dependency androidx.window:window to v1.2.0
• Update dependency com.airbnb.android:lottie-compose to v6.4.0
• Update dependency com.google.firebase:firebase-bom to v32.7.4
• Update dependency com.google.gms:google-services to v4.4.1
• Update dependency com.slack.lint.compose:compose-lint-checks to v1.3.1
• Update dependency com.squareup.okio:okio to v3.9.0
• Update dependency com.valentinilk.shimmer:compose-shimmer to v1.2.0
• Update dependency cybozu/LicenseList to from: "0.6.0"
• Update dependency danger-swiftlint to v0.35.0
• Update dependency danger-xcode_summary to v1.3.0
• Update dependency de.jensklingenberg.ktorfit:gradle-plugin to v1.8.1
• Update dependency fastlane to v2.219.0
• Update dependency gradle to v8.6
• Update dependency io.coil-kt:coil-compose to v2.6.0
• Update dependency io.github.qdsfdhvh:image-loader to v1.7.8
• Update dependency io.insert-koin:koin-core to v3.5.3
• Update dependency org.jetbrains.kotlinx:atomicfu to v0.23.2
• Update dependency org.jetbrains.kotlinx:kotlinx-coroutines-core to v1.8.0
• Update dependency org.jetbrains.kotlinx:kotlinx-datetime to v0.5.0
• Update dependency org.robolectric:robolectric to v4.11.1
• Update dependency pointfreeco/swift-dependencies to from: "1.2.2"
• Update dependency realm/SwiftLint to from: "0.54.0"
• Update dependency ruby to v3.3.0
• Update ghcr.io/realm/swiftlint Docker tag to v0.54.0
• Update ktorfit to v1.12.0 (de.jensklingenberg.ktorfit:ktorfit-ksp, de.jensklingenberg.ktorfit:ktorfit-lib)
• Update okhttp monorepo to v4.12.0 (com.squareup.okhttp3:logging-interceptor, com.squareup.okhttp3:okhttp)
• Update roborazzi to v1.11.0 (io.github.takahirom.roborazzi, io.github.takahirom.roborazzi:roborazzi-junit-rule, io.github.takahirom.roborazzi:roborazzi-compose, io.github.takahirom.roborazzi:roborazzi, io.github.takahirom.roborazzi:roborazzi-gradle-plugin)
• Update actions/cache action to v4
• Update actions/checkout action to v4
• Update actions/github-script action to v7
• Update actions/setup-java action to v4
• Update actions/upload-artifact action to v4
• Update dawidd6/action-download-artifact action to v3
• Update dependency androidx.compose:compose-bom to v2024
• Update dependency apple/swift-async-algorithms to v1
• Update dependency co.touchlab:kermit to v2
• Update github/codeql-action action to v3
• Update gradle/gradle-build-action action to v3
• Update gradle/wrapper-validation-action action to v2
• Update peter-evans/create-or-update-comment action to v4
• Update peter-evans/find-comment action to v3
• Update renovatebot/github-action action to v40
• Update gh-actions (EnricoMi/publish-unit-test-result-action, actions/setup-java, actions/upload-artifact, dawidd6/action-download-artifact, gradle/gradle-build-action, marocchino/sticky-pull-request-comment, renovatebot/github-action, reviewdog/action-setup, ruby/setup-ruby)
• 🔐 Create all rate-limited PRs at once 🔐

Other Branches

These updates are pending. To force PRs open, click the checkbox below.

• Update kotlin monorepo to v1.9.23 (org.jetbrains.kotlin.android, org.jetbrains.kotlin:kotlin-serialization, org.jetbrains.kotlin:kotlin-gradle-plugin)

Open

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

• Update composeMaterial3 to v1.2.1 (androidx.compose.material3:material3-window-size-class, androidx.compose.material3:material3)
• Update dependency androidx.datastore:datastore-preferences-core to v1.1.0-beta02
• Update showkase to v1.0.2 (com.airbnb.android:showkase-processor, com.airbnb.android:showkase)
• Update dependency airbnb/lottie-spm to from: "4.4.1"
• Update dependency com.google.firebase:firebase-crashlytics-ktx to v18.6.2
• Update dependency danger to v9.4.3
• Update dependency firebase/firebase-ios-sdk to from: "10.23.0"
• Update dependency org.jetbrains.compose:compose-gradle-plugin to v1.6.1
• Update multiplatformFirebase to v1.11.1 (dev.gitlive:firebase-config, dev.gitlive:firebase-auth)
• 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

Decide on KMP strategy, including what layers to share between the Android and iOS apps

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: packageRules[0]: packageRules cannot combine both matchUpdateTypes and versioning. Rule: {"groupName":"gh-actions","prPriority":-1,"matchManagers":["github-actions"],"matchUpdateTypes":["minor","patch"],"matchDatasources":["github-tags"],"versioning":"semver","automerge":true,"platformAutomerge":true,"pinDigests":true,"schedule":["after 10am before 5pm on tuesday"]}

This is a proposal to introduce CodeQL. CodeQL is a discovery tool for vulnerabilities and can visualize them by some integrations.

• https://codeql.github.com/
• https://github.com/github/codeql-action

状態: 1画面作り始めるために必要なものが揃っている。READMEにかけそうな内容を考えながらやると良さそう。

UI: UIをどういう書き方で書くのかが決まっている。Material、Theme、Compose Multiplatform使う？など
ビルド: フォーマットが楽にできたりする。CIでテストとビルドができる。(Actionsの切り方の設計などがあれば)
UI以外の設計周り: 一通り作るのに必要なもの(テスト、エラーハンドリング、DI、KMM)
iOS: 上記すべて
サーバーサイド / API: ここではスコープ外

In the conference-app-2022, the Build action time is reached 53m eventually.

DroidKaigi/conference-app-2022#647

It would be appreciated if to avoid such a long action time. doesn't it?

We can improve total action time by splitting the Build action into several actions.

like this:

• assemble & upload aab to somewhere
• spotlessCheck
• lint
• local unit tests & report the result

First of all, I think it is good to split assemble & upload aab to somewhere and another.
Ideally, however, lint and local unit tests should run even if spotlessCheck fails. This is because it is ideal to detect all errors at once and show them to the contributors.