[CI] (e2f7ab0) android/Jetchat

[wizard-ci-bot]

Automated wizard CI run

Source: wizard-pr
Trigger ID: e2f7ab0
App: android/Jetchat
App directory: apps/android/Jetchat
Workbench branch: wizard-ci-e2f7ab0-android-Jetchat
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-07-06T21:58:57.532Z
Duration: 408.5s

YARA Scanner

✓ 63 tool calls scanned, 0 violations detected

No violations: ✓ 63 clean scans

[wizard-ci-bot]

PR Evaluation Report

Summary

This PR integrates PostHog analytics into the Jetchat Android sample app. It adds the PostHog Android SDK, creates an Application subclass for initialization with API keys loaded from local.properties via BuildConfig, and instruments 11 events across login/logout, messaging, navigation, and UI interactions. User identification is implemented on login with reset() on logout.

Files changed	Lines added	Lines removed
10	+138	-2

Confidence score: 4/5 👍

• Username used as distinct_id: PostHog.identify(distinctId = username) uses a raw username string as the distinct ID, which may not be a stable unique identifier and risks collisions or fragmented data. A database user ID is preferred. [MEDIUM]
• No error tracking configured: errorTrackingConfig.autoCapture is not enabled in the PostHog config, and no manual exception capture is present. [MEDIUM]
• No .env example file updated: The setup report mentions adding posthog.apiKey and posthog.host to a local.properties.example as a TODO, but no such file is included in the PR. [MEDIUM]

---

File changes

Filename	Score	Description
app/build.gradle.kts	4/5	Adds PostHog dependency, enables buildConfig, loads API key/host from local.properties
AndroidManifest.xml	5/5	Registers Application class, adds android:label for screen view tracking
JetchatApplication.kt	4/5	New Application class with PostHog initialization, good config options but missing error tracking
MainViewModel.kt	3/5	Login/logout with identify/reset — but uses username as distinct_id
NavActivity.kt	5/5	Captures channel_switched and profile_viewed with relevant properties
JetchatDrawer.kt	5/5	Captures widget_added_to_home event
Conversation.kt	5/5	Captures message_sent with channel_name and message_length properties
UserInput.kt	5/5	Captures attachment, emoji, and voice message events with properties
libs.versions.toml	5/5	Adds PostHog version catalog entry
posthog-setup-report.md	4/5	Good documentation but is an extra file not strictly needed

---

App sanity check ⚠️

Criteria	Result	Description
App builds and runs	Yes	Valid Gradle config, proper imports, correct syntax throughout
Preserves existing env vars & configs	Yes	Existing configs preserved; only PostHog additions made
No syntax or type errors	Yes	All Kotlin files have valid syntax and correct API usage
Correct imports/exports	Yes	All PostHog imports are correct (com.posthog.PostHog, com.posthog.android.*)
Minimal, focused changes	Yes	All changes relate to PostHog integration
Pre-existing issues	None	No pre-existing issues detected

Issues

• No env example file: local.properties is gitignored by convention, and no local.properties.example is provided to document the required posthog.apiKey and posthog.host values for other developers. [MEDIUM]

Other completed criteria

• Build configuration correctly enables buildConfig = true for generated fields
• Version catalog properly defines PostHog dependency
• AndroidManifest correctly registers Application subclass
• android:label added to NavActivity for screen view tracking

---

PostHog implementation ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	com.posthog:posthog-android:3.31.0 added via version catalog
PostHog client initialized	Yes	PostHogAndroid.setup() called in JetchatApplication.onCreate() with proper config
capture()	Yes	11 meaningful capture calls across 5 files
identify()	Yes	Called on login with PostHog.reset() on logout
Error tracking	No	errorTrackingConfig.autoCapture not enabled, no manual exception capture
Reverse proxy	N/A	Android native app — reverse proxy not applicable

Issues

• No error tracking: The PostHog config does not set errorTrackingConfig.autoCapture = true and there are no manual `` captures. Error tracking is a rubric requirement. [MEDIUM]
• Username as distinct_id: PostHog.identify(distinctId = username) uses the login username directly. Usernames may not be unique database identifiers and could cause user merging issues. Should use a stable user ID. [MEDIUM]

Other completed criteria

• API key loaded from BuildConfig.POSTHOG_API_KEY (sourced from local.properties), not hardcoded
• Host correctly configured via BuildConfig.POSTHOG_HOST with default https://us.i.posthog.com
• PostHog.reset() correctly called on logout
• Session replay enabled
• Autocapture features enabled (lifecycle events, deep links, screen views)

---

PostHog insights and events ✅

Filename	PostHog events	Description
MainViewModel.kt	user_logged_in, user_logged_out	Auth lifecycle tracking with identify/reset
NavActivity.kt	channel_switched, profile_viewed	Navigation events with channel_name and profile_user_id properties
Conversation.kt	message_sent	Core action with channel_name and message_length properties
JetchatDrawer.kt	widget_added_to_home	Widget interaction tracking
UserInput.kt	attachment_type_selected, emoji_inserted, voice_message_started, voice_message_sent, voice_message_cancelled	Rich input interaction tracking with relevant properties

Issues

• No critical or medium issues with event quality.

Other completed criteria

• Events represent real user actions mapped to actual product flows
• Events enable product insights (login→message funnel, voice completion rate, feature adoption)
• Events include relevant contextual properties (channel_name, message_length, selector_type, emoji, profile_user_id)
• No PII in event properties — person data handled via identify
• Event names are descriptive and use consistent snake_case convention

---

Reviewed by wizard workbench PR evaluator