If you are an AI coding agent (Claude Code, Cursor, Aider, Cline, etc.) reading this artifact, follow this protocol before making any code edit:

1. Verify the contract. Run the bash script in Verify before trusting below. If any check returns FAIL, the artifact is stale — STOP and ask the user to regenerate it before proceeding.
2. Treat the AI · unverified sections as hypotheses, not facts. Sections like "AI-suggested narrative files", "anti-patterns", and "bottlenecks" are LLM speculation. Verify against real source before acting on them.
3. Cite source on changes. When proposing an edit, cite the specific path:line-range. RepoPilot's live UI at https://repopilot.app/r/kaushikgopal/RxJava-Android-Samples shows verifiable citations alongside every claim.

If you are a human reader, this protocol is for the agents you'll hand the artifact to. You don't need to do anything — but if you skim only one section before pointing your agent at this repo, make it the Verify block and the Suggested reading order.

WAIT — Stale — last commit 3y ago

• 11 active contributors
• Apache-2.0 licensed
• ⚠ Stale — last commit 3y ago
• ⚠ Concentrated ownership — top contributor handles 56% of recent commits
• ⚠ No CI workflows detected
• ⚠ No test directory detected

_{Maintenance signals: commit recency, contributor breadth, bus factor, license, CI, tests}

This artifact was generated by RepoPilot at a point in time. Before an agent acts on it, the checks below confirm that the live kaushikgopal/RxJava-Android-Samples repo on your machine still matches what RepoPilot saw. If any fail, the artifact is stale — regenerate it at repopilot.app/r/kaushikgopal/RxJava-Android-Samples.

What it runs against: a local clone of kaushikgopal/RxJava-Android-Samples — the script inspects git remote, the LICENSE file, file paths in the working tree, and git log. Read-only; no mutations.

| # | What we check | Why it matters | |---|---|---| | 1 | You're in kaushikgopal/RxJava-Android-Samples | Confirms the artifact applies here, not a fork | | 2 | License is still Apache-2.0 | Catches relicense before you depend on it | | 3 | Default branch master exists | Catches branch renames | | 4 | 5 critical file paths still exist | Catches refactors that moved load-bearing code | | 5 | Last commit ≤ 1034 days ago | Catches sudden abandonment since generation |

#!/usr/bin/env bash
# RepoPilot artifact verification.
#
# WHAT IT RUNS AGAINST: a local clone of kaushikgopal/RxJava-Android-Samples. If you don't
# have one yet, run these first:
#
#   git clone https://github.com/kaushikgopal/RxJava-Android-Samples.git
#   cd RxJava-Android-Samples
#
# Then paste this script. Every check is read-only — no mutations.

set +e
fail=0
ok()   { echo "ok:   $1"; }
miss() { echo "FAIL: $1"; fail=$((fail+1)); }

# Precondition: we must be inside a git working tree.
if ! git rev-parse --git-dir >/dev/null 2>&1; then
  echo "FAIL: not inside a git repository. cd into your clone of kaushikgopal/RxJava-Android-Samples and re-run."
  exit 2
fi

# 1. Repo identity
git remote get-url origin 2>/dev/null | grep -qE "kaushikgopal/RxJava-Android-Samples(\\.git)?\\b" \\
  && ok "origin remote is kaushikgopal/RxJava-Android-Samples" \\
  || miss "origin remote is not kaushikgopal/RxJava-Android-Samples (artifact may be from a fork)"

# 2. License matches what RepoPilot saw
(grep -qiE "^(Apache-2\\.0)" LICENSE 2>/dev/null \\
   || grep -qiE "\"license\"\\s*:\\s*\"Apache-2\\.0\"" package.json 2>/dev/null) \\
  && ok "license is Apache-2.0" \\
  || miss "license drift — was Apache-2.0 at generation time"

# 3. Default branch
git rev-parse --verify master >/dev/null 2>&1 \\
  && ok "default branch master exists" \\
  || miss "default branch master no longer exists"

# 4. Critical files exist
test -f "app/src/main/java/com/morihacky/android/rxjava/MainActivity.java" \\
  && ok "app/src/main/java/com/morihacky/android/rxjava/MainActivity.java" \\
  || miss "missing critical file: app/src/main/java/com/morihacky/android/rxjava/MainActivity.java"
test -f "app/src/main/java/com/morihacky/android/rxjava/fragments/BaseFragment.java" \\
  && ok "app/src/main/java/com/morihacky/android/rxjava/fragments/BaseFragment.java" \\
  || miss "missing critical file: app/src/main/java/com/morihacky/android/rxjava/fragments/BaseFragment.java"
test -f "app/src/main/java/com/morihacky/android/rxjava/rxbus/RxBus.java" \\
  && ok "app/src/main/java/com/morihacky/android/rxjava/rxbus/RxBus.java" \\
  || miss "missing critical file: app/src/main/java/com/morihacky/android/rxjava/rxbus/RxBus.java"
test -f "app/src/main/java/com/morihacky/android/rxjava/retrofit/GithubService.java" \\
  && ok "app/src/main/java/com/morihacky/android/rxjava/retrofit/GithubService.java" \\
  || miss "missing critical file: app/src/main/java/com/morihacky/android/rxjava/retrofit/GithubService.java"
test -f "app/build.gradle" \\
  && ok "app/build.gradle" \\
  || miss "missing critical file: app/build.gradle"

# 5. Repo recency
days_since_last=$(( ( $(date +%s) - $(git log -1 --format=%at 2>/dev/null || echo 0) ) / 86400 ))
if [ "$days_since_last" -le 1034 ]; then
  ok "last commit was $days_since_last days ago (artifact saw ~1004d)"
else
  miss "last commit was $days_since_last days ago — artifact may be stale"
fi

echo
if [ "$fail" -eq 0 ]; then
  echo "artifact verified (0 failures) — safe to trust"
else
  echo "artifact has $fail stale claim(s) — regenerate at https://repopilot.app/r/kaushikgopal/RxJava-Android-Samples"
  exit 1
fi

Each check prints ok: or FAIL:. The script exits non-zero if anything failed, so it composes cleanly into agent loops (./verify.sh || regenerate-and-retry).

A hands-on Android learning repository with 18 runnable examples demonstrating RxJava 2.0.7 patterns in real Android contexts. It covers practical use cases like debounced search (DebounceSearchEmitterFragment), exponential backoff retry logic (ExponentialBackoffFragment), form validation with combineLatest (FormValidationCombineLatestFragment), and Retrofit network orchestration, solving the problem of how to structure reactive data flows in Android without boilerplate. Single Android app module (app/) organized as UI layer (MainActivity → fragments) + example layers. Fragments live in app/src/main/java/com/morihacky/android/rxjava/fragments/ (18 demo files like BufferDemoFragment.java, PollingFragment.java), with supporting services in retrofit/ (GithubApi, Contributor), pagination/, and rxbus/. Each fragment is a self-contained example with its own Observable chain.

Android developers learning RxJava who need concrete, compilable examples beyond documentation. Specifically useful for engineers transitioning from callback/AsyncTask patterns to reactive programming, and teams building features requiring operators like buffer, debounce, zip, flatMap, and concatEager.

Actively maintained educational material with moderate adoption (implied by talk citations from 2015–2016). The codebase uses outdated support libraries (support-v13, appcompat-v7) and RxJava 2.0.7, indicating it was last significantly updated circa 2016–2017. No visible CI/CD, sparse test coverage (only one ApplicationTest.java file), and the README notes 'constant state of WIP', so treat it as a reference implementation, not production-ready infrastructure.

RxJava 2.0.7 is now EOL (current is RxJava 3.x); Retrofit2 and OkHttp3 versions are pinned without constraints. Single maintainer (kaushikgopal) with no recent activity visible. Dependencies on deprecated Android Support libraries (multidex, appcompat-v7) mean direct copy-paste into modern Android projects risks compilation errors. No license clarity on reusing examples in commercial work.

No visible active development; the repository is in archival/educational state. The most recent signal is Kotlin support (RotationPersist3Fragment.kt), but no branches, PRs, or recent commits are indicated in the provided data.

1. Clone the repo: git clone https://github.com/kaushikgopal/RxJava-Android-Samples.git. 2. Open in Android Studio: File > Open > [cloned directory]. 3. Let Gradle sync (uses Gradle wrapper; build.gradle has jcenter() + retrolambda plugin for Java 8 lambdas). 4. Run on emulator or device via ./gradlew installDebug or Android Studio's Run button.

Daily commands:

1. Android Studio: click Run (▶) or Shift+F10. 2. Command line: ./gradlew installDebug && adb shell am start -n com.morihacky.android.rxjava/.MainActivity. 3. Emulator must be running (or device connected). No custom server needed; examples use live GitHub API or synthetic data.

• app/src/main/java/com/morihacky/android/rxjava/MainActivity.java — Entry point of the application; orchestrates fragment navigation for all RxJava examples
• app/src/main/java/com/morihacky/android/rxjava/fragments/BaseFragment.java — Abstract base class for all example fragments; establishes lifecycle and subscription management patterns used throughout
• app/src/main/java/com/morihacky/android/rxjava/rxbus/RxBus.java — Core event-bus implementation using RxJava Subjects; demonstrates a fundamental reactive pattern used in multiple examples
• app/src/main/java/com/morihacky/android/rxjava/retrofit/GithubService.java — Retrofit API service wrapper showcasing real-world async HTTP integration with RxJava observables
• app/build.gradle — Build configuration with RxJava, Retrofit, and Kotlin dependencies; essential for understanding project versioning and plugin setup
• app/src/main/kotlin/com/morihacky/android/rxjava/ext/RxExt.kt — Kotlin extension functions for RxJava operators; demonstrates modern reactive patterns and simplifies code in Kotlin examples
• app/src/main/java/com/morihacky/android/rxjava/MyApp.java — Application singleton; likely manages global state and initialization for the demo app

Add a New RxJava Example Fragment

1. Create new fragment class extending BaseFragment in app/src/main/java/com/morihacky/android/rxjava/fragments/ (app/src/main/java/com/morihacky/android/rxjava/fragments/BaseFragment.java)
2. Override onCreateView() and implement observable chain using RxJava operators (app/src/main/java/com/morihacky/android/rxjava/fragments/DebounceSearchEmitterFragment.java)
3. Add subscription to CompositeSubscription in onCreateView() (inherited from BaseFragment) (app/src/main/java/com/morihacky/android/rxjava/fragments/BaseFragment.java)
4. Create corresponding layout XML in app/src/main/res/layout/fragment_example_name.xml (app/src/main/res/layout/fragment_debounce.xml)
5. Register fragment in MainActivity to add it to the example list navigation (app/src/main/java/com/morihacky/android/rxjava/MainActivity.java)

Add a New Network API Example with Retrofit

1. Define new API endpoints in app/src/main/java/com/morihacky/android/rxjava/retrofit/GithubApi.java (app/src/main/java/com/morihacky/android/rxjava/retrofit/GithubApi.java)
2. Add wrapper methods in GithubService returning Observable<T> for each endpoint (app/src/main/java/com/morihacky/android/rxjava/retrofit/GithubService.java)
3. Create model classes (Contributor, User) for response mapping in retrofit/ package (app/src/main/java/com/morihacky/android/rxjava/retrofit/Contributor.java)
4. Create new fragment that calls GithubService methods and chains operators (flatMap, zip, etc.) (app/src/main/java/com/morihacky/android/rxjava/fragments/RetrofitFragment.java)
5. Ensure subscriptions are added to CompositeSubscription via BaseFragment lifecycle (app/src/main/java/com/morihacky/android/rxjava/fragments/BaseFragment.java)

Implement Event Bus Communication Between Fragments

1. Create event model class or use existing types for message payload (app/src/main/java/com/morihacky/android/rxjava/rxbus/RxBusDemo_TopFragment.java)
2. Get RxBus singleton and call post(eventObject) from sender fragment (app/src/main/java/com/morihacky/android/rxjava/rxbus/RxBus.java)
3. In receiver fragment, subscribe to toObservable(eventClass) and handle emissions (app/src/main/java/com/morihacky/android/rxjava/rxbus/RxBusDemo_Bottom1Fragment.java)
4. Add subscription to CompositeSubscription to ensure cleanup on fragment destroy (app/src/main/java/com/morihacky/android/rxjava/fragments/BaseFragment.java)

Add a New Kotlin RxJava Extension Operator

1. Open Kotlin extensions file and add extension function to Observable<T> (app/src/main/kotlin/com/morihacky/android/rxjava/ext/RxExt.kt)
2. Implement operator logic using existing RxJava operators (map, filter, etc.) (app/src/main/kotlin/com/morihacky/android/rxjava/ext/RxExt.kt)
3. Use extension in any Kotlin fragment by calling observable.customOperator() (app/src/main/kotlin/com/morihacky/android/rxjava/fragments/PlaygroundFragment.kt)

1. retrolambda plugin (gradle-retrolambda:3.6.0) requires Java 8 as JDK; older Android Studio versions may not configure this automatically. 2. RxJava 2.0.7 removed Observable.create(OnSubscribe) — code examples use Observer + onNext/onError/onComplete callbacks, which differs from RxJava 1.x; copy-paste into newer projects risks import mismatches. 3. AndroidSchedulers.mainThread() is implicit; examples assume RxAndroid dependency is present (not explicitly shown in the gradle snippet provided). 4. GithubApi live endpoints may rate-limit or change; RotationPersist examples use synthetic data, but RetrofitFragment makes real API calls. 5. ButterKnife @Bind annotations are pre-2.0; if you update ButterKnife, syntax changes to @BindView.

• Subject (PublishSubject, BehaviorSubject, ReplaySubject) — Subjects bridge imperative code (UI events) with reactive streams; DebounceSearchEmitterFragment and DoubleBindingTextViewFragment rely on them to convert TextWatcher callbacks into Observables
• Backpressure & buffer() — buffer() accumulates emissions and handles producer/consumer speed mismatches; BufferDemoFragment shows how to avoid 'MissingBackpressureException' when source emits faster than subscriber consumes
• Scheduler (io, computation, mainThread) — Schedulers control thread boundaries; ConcurrencyWithSchedulersDemoFragment and all network examples use Schedulers.io() to offload blocking I/O and AndroidSchedulers.mainThread() to return to UI thread safely
• Exponential backoff & retryWhen() — retryWhen() + delay() composite operator implements fault-tolerant network retry; ExponentialBackoffFragment demonstrates how to avoid overwhelming a failing server
• Hot vs Cold Observables (multicast, replay) — PseudoCacheFragment and RotationPersist examples distinguish between eager (hot) and lazy (cold) sources; RotationPersist uses retained Subjects to maintain hot streams across rotation
• Operator composition (zip, flatMap, combineLatest, concat) — These operators orchestrate multiple Observables; FormValidationCombineLatestFragment uses combineLatest to merge email/password fields into a single validation stream, and pagination examples use flatMap for sequential page loads
• Retained Fragments & lifecycle persistence — RotationPersist1-3Fragment examples show how Subjects in retained Fragments survive Activity rotation without memory leaks; critical pattern for long-running async work

• ReactiveX/RxJava — Official RxJava 2.x repository; source of truth for operator documentation and version history
• ReactiveX/RxAndroid — RxJava Android bindings (AndroidSchedulers, lifecycle integration); required dependency for this repo's Scheduler examples
• square/retrofit — Retrofit HTTP client used throughout the GithubService examples; needed to understand API Observable integration
• JakeWharton/RxBinding — RxJava bindings for Android UI widgets; complements DebounceSearchEmitterFragment and DoubleBindingTextViewFragment patterns
• JakeWharton/RxRelay — Never-completing Subject implementation used in RxBus example (fragment 11); handles event bus without termination

To work on one of these in Claude Code or Cursor, paste: Implement the "<title>" PR idea from CLAUDE.md, working through the checklist as the task list.

Add unit tests for RxBus implementation

The RxBus class (app/src/main/java/com/morihacky/android/rxjava/rxbus/RxBus.java) is a critical utility used across multiple demo fragments (RxBusDemoFragment, RxBusDemo_Bottom1Fragment, etc.) but has no corresponding unit tests. This is a learning repo, so demonstrating proper testing patterns for RxJava event bus implementations would be valuable for contributors. Tests should cover subject behavior, subscription/unsubscription, and thread safety.

• [ ] Create app/src/test/java/com/morihacky/android/rxjava/rxbus/RxBusTest.java
• [ ] Add tests for post() and toObservable() methods with various payload types
• [ ] Add tests for multiple subscribers receiving the same event
• [ ] Add tests for unsubscription behavior and memory leak prevention
• [ ] Update build.gradle to include JUnit and Mockito dependencies if missing

Add instrumented tests for retrofit/network fragments

The repo has multiple network-dependent fragments (RetrofitFragment, RetrofitAsyncTaskDeathFragment, PaginationFragment, PaginationAutoFragment) that interact with GithubApi, but app/src/androidTest only contains a placeholder ApplicationTest.java. Adding proper instrumented tests would demonstrate best practices for testing RxJava-based network calls with mocked responses and would help contributors understand testing patterns.

• [ ] Create app/src/androidTest/java/com/morihacky/android/rxjava/retrofit/GithubApiTest.java with mocked retrofit responses
• [ ] Add tests for pagination examples using MockWebServer or similar
• [ ] Create app/src/androidTest/java/com/morihacky/android/rxjava/fragments/RetrofitFragmentTest.java demonstrating fragment testing with RxJava
• [ ] Document how to mock GithubService in a comment or test setup
• [ ] Add MockWebServer dependency to build.gradle if needed

Convert Java demo fragments to Kotlin with extension utilities

The repo has a Kotlin extension file (app/src/main/kotlin/com/morihacky/android/rxjava/ext/RxExt.kt) and one Kotlin fragment (RotationPersist3Fragment.kt), but the majority of fragments remain in Java. Systematically converting high-value examples (like FormValidationCombineLatestFragment, DebounceSearchEmitterFragment, or ConcurrencyWithSchedulersDemoFragment) to Kotlin would demonstrate modern RxJava patterns and benefit learners. Start with fragments that have the most instructional value.

• [ ] Convert app/src/main/java/com/morihacky/android/rxjava/fragments/FormValidationCombineLatestFragment.java to Kotlin, leveraging RxExt.kt utilities
• [ ] Convert app/src/main/java/com/morihacky/android/rxjava/fragments/DebounceSearchEmitterFragment.java to Kotlin to show debounce patterns in modern syntax
• [ ] Expand app/src/main/kotlin/com/morihacky/android/rxjava/ext/RxExt.kt with additional extension functions discovered during conversion (e.g., safe view subscriptions)
• [ ] Update README.md to mark converted fragments with a Kotlin badge or indicator
• [ ] Ensure kotlin-stdlib and kotlin-reflect versions in build.gradle are current

• Add unit tests for BufferDemoFragment and TimingDemoFragment (no test coverage visible for operator logic); could use RobolectricTestRunner + TestScheduler to verify emission counts and timing.
• Document the relationship between PublishSubject vs BehaviorSubject in DoubleBindingTextViewFragment.java and RotationPersist examples with inline comments and a comparison table in README; currently implicit and confusing for learners.
• Add a new example demonstrating flatMapConcat vs flatMap ordering semantics (mentioned in RxJava docs but not present in the 18 examples); would complement PaginationAutoFragment and help with async operation ordering.

• High · Outdated RxJava Dependency — app/build.gradle - compile 'io.reactivex.rxjava2:rxjava:2.0.7'. The codebase uses RxJava 2.0.7 (released in 2016), which is significantly outdated and likely contains known security vulnerabilities and bugs. Current stable versions are RxJava 3.x with numerous patches and improvements. Fix: Update to the latest stable version of RxJava 3.x (e.g., 3.1.x or higher). Review and test compatibility with the application code after updating.
• High · Outdated Retrofit Dependency — app/build.gradle - compile "com.squareup.retrofit2:retrofit:${retrofitVersion}". The build.gradle uses an outdated version of Retrofit2 (variable reference '${retrofitVersion}' - likely 2.x based on context). Older versions may have security vulnerabilities in HTTP handling and SSL/TLS verification. Fix: Update Retrofit2 to the latest stable version (2.9.0 or higher). Ensure OkHttp is also updated to 4.x or higher for better security defaults.
• High · Outdated OkHttp Dependency — app/build.gradle - compile "com.squareup.okhttp3:okhttp:${okhttpVersion}". The OkHttp version is specified by variable '${okhttpVersion}' and appears to be from an older release cycle. OkHttp 3.x and earlier have known security issues. Version 4.0+ introduced significant security improvements. Fix: Update OkHttp to 4.9.x or higher. Ensure all dependent libraries are compatible with the new version.
• High · Outdated Support Library — app/build.gradle - com.android.support:* dependencies. Support libraries are deprecated and replaced by AndroidX. Using outdated support libraries means missing critical security patches and bug fixes for UI components and lifecycle handling. Fix: Migrate to AndroidX libraries. Replace support-v13, appcompat-v7, recyclerview-v7 with their androidx equivalents (androidx.appcompat:appcompat, androidx.recyclerview:recyclerview, etc.).
• Medium · Outdated ButterKnife Dependency — app/build.gradle - com.jakewharton:butterknife. ButterKnife version is specified by variable '${butterKnifeVersion}' and appears to be from an older release. View binding libraries may have had security or stability improvements in newer versions. Fix: Update ButterKnife to the latest stable version or consider migrating to ViewBinding (built-in since AGP 3.6) for better type safety and performance.
• Medium · Deprecated Volley HTTP Library — app/build.gradle - compile 'com.mcxiaoke.volley:library:1.0.19'. Volley (1.0.19) is an older HTTP library. While functional, modern alternatives like OkHttp or Retrofit with OkHttp provide better performance, security defaults, and maintenance. Fix: Migrate from Volley to Retrofit2 with OkHttp for all HTTP operations to maintain consistency and benefit from better security defaults.
• Medium · Missing Proguard/R8 Configuration Review — app/proguard-rules.pro. While a proguard-rules.pro file exists, there is no visibility into its contents. Inadequate obfuscation rules can expose sensitive code or leave debug information in production builds. Fix: Review proguard-rules.pro to ensure: 1) Third-party libraries are properly configured, 2) Sensitive classes are obfuscated, 3) Debug information is stripped, 4) Rules align with library recommendations (Retrofit, OkHttp, RxJava).
• Medium · Deprecated retrolambda Plugin — build.gradle - classpath 'me.tat. The gradle-retrolambda plugin is outdated and unnecessary for modern Android development. Java 8+ is now the standard minimum, and retrolambda was a workaround for older API levels. Fix: undefined

LLM-derived; treat as a starting point, not a security audit.

• Open issues — current backlog
• Recent PRs — what's actively shipping
• Source on GitHub

Generated by RepoPilot. Verdict based on maintenance signals — see the live page for receipts. Re-run on a new commit to refresh.