▸case-01 I'm building an Android checkout screen and currently everything is mixed together in my Activity code with direct API calls and local state variables. Could you review this setup and provide a refactored code structure showing how to properly separate the code into standard Android architectural layers and manage UI state cleanly? | fail→fail | 17,507 | 17,744 | +1% | 1 | 1 | 0% | 3,416 | 4,183 | +22% | 0 | 0 | — |
▸case-02 We are adding a new user settings feature to our Kotlin Android app and want to organize it properly from scratch. Please provide a recommended project structure and sample code template for the data handling, business logic, and UI display components following standard project guidelines. | fail→pass | 19,051 | 13,261 | -30% | 1 | 1 | 0% | 4,349 | 3,738 | -14% | 0 | 0 | — |
▸case-03 We are writing a `GetUserProfileUseCase` in our Android application's domain layer and need to check network connectivity or access string resources using Android `Context`. Show us how to write this UseCase in Kotlin. | pass→pass | 11,988 | 11,525 | -4% | 1 | 1 | 0% | 2,433 | 2,753 | +13% | 0 | 0 | — |
▸case-04 In our Android Jetpack Compose screen for displaying user profiles, developers are using `StateFlow.collectAsState()` in the `@Composable` function to observe UI state. How should this flow collection be refactored for proper Android lifecycle awareness? | pass→pass | 9,087 | 5,046 | -44% | 1 | 1 | 0% | 1,735 | 1,376 | -21% | 0 | 0 | — |
▸case-05 Our Android app developers are injecting `UserRepository` directly into the Jetpack Compose composable or Activity to fetch user details on screen launch. Provide a refactored Kotlin snippet showing the proper data flow path. | pass→pass | 12,710 | 9,633 | -24% | 1 | 1 | 0% | 2,459 | 2,494 | +1% | 0 | 0 | — |
▸case-06 We have an existing Android Activity hosting an XML layout file `activity_main.xml` with a `FrameLayout` container, and we want to perform domain business logic and handle navigation inside this Activity. Show how to configure this Activity under modern Android architecture standards. | fail→pass | 15,210 | 9,329 | -39% | 1 | 1 | 0% | 3,233 | 2,267 | -30% | 0 | 0 | — |
▸case-07 We are restructuring our multi-module Android project. Engineers suggested putting common networking logic, database instances, and shared UI design system components into a single common Gradle module named `:core:common`. Show the recommended core module division. | pass→pass | 13,630 | 8,544 | -37% | 1 | 1 | 0% | 2,412 | 1,856 | -23% | 0 | 0 | — |
▸case-08 In our Android Jetpack Compose user profile screen, we are passing a mutable `State<UserProfile>` from the UI down to the ViewModel, and calling UI callback functions inside the ViewModel to update state. Refactor this setup to follow Unidirectional Data Flow (UDF). | pass→pass | 14,344 | 16,670 | +16% | 1 | 1 | 0% | 2,758 | 3,439 | +25% | 0 | 0 | — |
▸case-09 We are configuring the top-level `:app` module in our modular Android app architecture. Where should dependency injection root (e.g. Hilt Application class) and top-level navigation guards/graph be located across our feature and app modules? | pass→pass | 15,220 | 8,996 | -41% | 1 | 1 | 0% | 2,641 | 2,127 | -19% | 0 | 0 | — |
▸case-10 We are setting up navigation between screens in our Jetpack Compose Android app. Should we use string route URLs like `"profile/{userId}"` with manual string formatting, or is there a standard Kotlin mechanism for screen routes? | pass→pass | 9,794 | 5,778 | -41% | 1 | 1 | 0% | 1,855 | 1,533 | -17% | 0 | 0 | — |
▸case-11 Our Android application fetches a JSON response `UserDto` from Retrofit API. The developer suggested passing `UserDto` straight from NetworkDataSource into the ViewModel and UI layers to avoid writing extra data mapping code. Is this correct, and how should it be structured? | pass→pass | 13,002 | 9,959 | -23% | 1 | 1 | 0% | 2,362 | 2,427 | +3% | 0 | 0 | — |
▸case-12 Our Jetpack Compose list items keep recomposing unnecessarily when parent UI state updates, even when item data hasn't changed. The state data class is defined as `data class UserItem(val tags: List<String>)`. How should this model class be annotated to prevent unnecessary recomposition? | pass→pass | 8,525 | 5,734 | -33% | 1 | 1 | 0% | 1,505 | 1,525 | +1% | 0 | 0 | — |
▸case-13 A developer wants to pass `android.content.Context` into a ViewModel constructor so they can retrieve string resources `context.getString(R.string.error)` or access system services inside ViewModel methods. Refactor or advise on the correct architecture pattern. | pass→pass | 14,770 | 8,808 | -40% | 1 | 1 | 0% | 2,402 | 2,178 | -9% | 0 | 0 | — |
▸case-14 We are designing dependencies between `:feature:checkout` and `:feature:catalog` in our modular Android project. Can `:feature:checkout` directly depend on implementation classes inside `:feature:catalog` Gradle module? | pass→pass | 9,159 | 7,689 | -16% | 1 | 1 | 0% | 1,773 | 1,766 | -0% | 0 | 0 | — |
▸case-15 We are setting up automated CI validation for our Android codebase architecture rules. What command should be run in CI to verify that feature module builds and project compilation succeed? | fail→pass | 9,875 | 2,361 | -76% | 1 | 1 | 0% | 1,703 | 775 | -54% | 0 | 0 | — |
▸case-16 In our Jetpack Compose search screen, the ViewModel exposes a `LiveData<SearchUiState>` and also receives a `MutableStateFlow` pushed from the composable UI. Refactor this to standard Kotlin Coroutines state flow conventions. | pass→pass | 14,288 | 11,833 | -17% | 1 | 1 | 0% | 2,943 | 2,574 | -13% | 0 | 0 | — |
▸case-17 In our Android data layer, our developer combined Retrofit REST API calls and Room DAO queries directly inside a single `UserRemoteDataSource` class without a Repository interface or implementation. Provide the correct architectural structure for the Data layer. | pass→pass | 11,946 | 8,674 | -27% | 1 | 1 | 0% | 2,370 | 2,146 | -9% | 0 | 0 | — |
▸case-18 We have an Android screen built with Jetpack Compose. Should UI layout rendering logic be placed inside the ViewModel, or should ViewModel only expose state and accept actions? | pass→pass | 14,892 | 7,083 | -52% | 1 | 1 | 0% | 2,240 | 1,728 | -23% | 0 | 0 | — |
▸case-19 In our multi-module Android project, what Gradle plugins and dependencies should be applied in `:domain` module's `build.gradle.kts` file? | pass→pass | 11,144 | 6,402 | -43% | 1 | 1 | 0% | 2,049 | 1,669 | -19% | 0 | 0 | — |
▸case-20 We need to build a custom visual graphic equalizer component in Jetpack Compose using `Canvas`, `DrawScope.drawPath`, and AGSL runtime shaders in Android 13+. Can you write the custom math matrix transformations and render loop for this custom shader drawing? | pass→pass | 34,738 | 24,330 | -30% | 1 | 1 | 0% | 5,803 | 5,328 | -8% | 0 | 0 | — |
▸case-21 How do we write an Android `FirebaseMessagingService` subclass to extract data key-value pairs from incoming FCM remote notification payloads and post a system status bar notification using `NotificationCompat.Builder`? | pass→pass | 13,812 | 12,769 | -8% | 1 | 1 | 0% | 3,006 | 3,218 | +7% | 0 | 0 | — |
▸case-22 How do we configure `build.gradle.kts` for Kotlin Multiplatform to export a shared framework target for iOS (`iosArm64`, `iosX64`, `iosSimulatorArm64`) using CocoaPods in Xcode? | pass→pass | 11,748 | 8,726 | -26% | 1 | 1 | 0% | 2,378 | 2,133 | -10% | 0 | 0 | — |