[CI] (3393d57) react-native/expo-react-native-hacker-news

[wizard-ci-bot]

Automated wizard CI run

Source: wizard-pr
Trigger ID: 3393d57
App: react-native/expo-react-native-hacker-news
App directory: apps/react-native/expo-react-native-hacker-news
Workbench branch: wizard-ci-3393d57-react-native-expo-react-native-hacker-news
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-03-17T00:32:56.602Z
Duration: 457.9s

[wizard-ci-bot]

I have sufficient information from the diff and the provided documentation to complete the evaluation. Let me analyze the PR comprehensively.

---

PR Evaluation Report

Summary

This PR integrates PostHog analytics into an Expo React Native Hacker News client app. It adds the posthog-react-native SDK, creates a singleton PostHog client configuration, wraps the app in PostHogProvider, implements screen tracking via a custom ScreenTracker component, and adds 10 custom capture() calls across multiple components for user interactions like story taps, comment navigation, and external link opens. No user identification or error tracking is implemented.

Files changed	Lines added	Lines removed
11	+208	-27

Confidence score: 4/5 👍

• No user identification (identify): The app tracks many user actions but never calls posthog.identify(). For a Hacker News reader app without auth this may be acceptable, but it limits the ability to link sessions and build person profiles. [MEDIUM]
• No error tracking: No captureException or error boundary integration is set up, which is a standard part of PostHog integration. [MEDIUM]
• No .env.example committed: The .env file is gitignored (correctly), but no .env.example or equivalent is committed to document the required environment variables (POSTHOG_PROJECT_TOKEN, POSTHOG_HOST). The setup report mentions configuring .env but that file isn't available to other developers cloning the repo. [MEDIUM]
• Unnecessary setup report file committed: posthog-setup-report.md is a wizard-generated report that shouldn't be part of the codebase. [LOW]

---

File changes

Filename	Score	Description
src/config/posthog.ts	4/5	New PostHog singleton client with env-based config via expo-constants. Good defensive check for unconfigured state.
app.config.js	4/5	Correctly exposes env vars through Expo constants extra field.
app/_layout.tsx	4/5	Wraps app in PostHogProvider, adds custom ScreenTracker component for route-based screen tracking.
app/[itemId].tsx	4/5	Adds 3 contextual capture calls for user profile views, external links, and parent story navigation.
components/posts/Post.tsx	4/5	Adds 3 capture calls for story taps, comment threads, and external links with relevant properties.
components/posts/Posts.tsx	3/5	Tracks infinite scroll loads — functional but may be noisy at scale.
components/comments/comment.tsx	4/5	Adds 2 capture calls for user profile views and comment thread navigation.
components/Select.tsx	5/5	Cleanly tracks story type filter changes with from/to properties.
package.json	5/5	Adds posthog-react-native dependency correctly.
.gitignore	5/5	Adds .env to gitignore — correct.
posthog-setup-report.md	2/5	Wizard-generated report file — shouldn't be committed to the codebase.

---

App sanity check ⚠️

Criteria	Result	Description
App builds and runs	Yes	Valid TypeScript/JSX, correct imports from posthog-react-native and expo-constants. No syntax errors visible.
Preserves existing env vars & configs	Yes	Existing layout structure, query client, and safe area provider are preserved. app.config.js extends existing app.json correctly.
No syntax or type errors	Yes	All code follows valid TypeScript patterns. Types are cast appropriately.
Correct imports/exports	Yes	PostHog, PostHogProvider, usePostHog correctly imported from posthog-react-native. Constants from expo-constants.
Minimal, focused changes	No	The posthog-setup-report.md is an unnecessary generated file.
Pre-existing issues	None	—

Issues

• Unnecessary report file: posthog-setup-report.md is a wizard-generated setup report that shouldn't be committed to the codebase. It adds noise and no runtime value. [LOW]

Other completed criteria

• Environment variables are loaded from .env via app.config.js → expo-constants — correct Expo pattern
• Build configuration is valid — package.json dependency added correctly
• Existing app structure and functionality preserved intact

---

PostHog implementation ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-react-native: ^4.37.3 added to package.json dependencies
PostHog client initialized	Yes	Singleton PostHog instance created in src/config/posthog.ts with env-based API key and host. Wrapped in PostHogProvider in _layout.tsx. Defensive disabled flag when not configured.
capture()	Yes	10 distinct capture calls across 6 files covering story interactions, navigation, link opens, scroll, and filter changes
identify()	N/A	This is a Hacker News reader app with no user authentication — there are no user accounts to identify against
Error tracking	No	No captureException calls, no error boundary integration, no exception autocapture configuration
Reverse proxy	N/A	React Native app — reverse proxy is not applicable for mobile SDKs

Issues

• No error tracking: The integration does not set up any error tracking. The posthog-react-native SDK supports captureException and the PostHogProvider can be configured with error boundary integration. This is a missed opportunity for production crash visibility. [MEDIUM]
• No .env.example file: While .env is correctly gitignored, there is no .env.example or similar documentation file committed to tell developers which environment variables are needed (POSTHOG_PROJECT_TOKEN, POSTHOG_HOST). The setup report mentions it but isn't a proper env template. [MEDIUM]

Other completed criteria

• API key loaded from environment variable via expo-constants extra config — not hardcoded
• Host correctly configured through environment variable
• Screen tracking implemented via custom ScreenTracker component using usePathname and posthog.screen()
• PostHogProvider wraps entire app with sensible autocapture config (touch capture enabled, screen capture disabled in favor of manual tracking)
• Defensive initialization: SDK is disabled when API key is missing or placeholder value
• captureAppLifecycleEvents: true enabled for automatic app open/background tracking

---

PostHog insights and events ⚠️

Filename	PostHog events	Description
app/_layout.tsx	screen (via posthog.screen())	Tracks every screen navigation with previous screen and route params
components/Select.tsx	story_type_changed	Captures filter changes with from/to type properties
components/posts/Post.tsx	story_tapped, comment_thread_opened, external_link_opened	Core story interaction events with story metadata
components/posts/Posts.tsx	more_stories_loaded	Infinite scroll pagination tracking with page number
components/comments/comment.tsx	user_profile_viewed, comment_thread_navigated	Comment-level interactions with author and reply context
app/[itemId].tsx	user_profile_viewed_from_item, item_external_link_opened, parent_story_navigated	Item detail page interactions with navigation context

Issues

• more_stories_loaded may be noisy: This event fires on every infinite scroll page load, which could generate high event volume. Consider sampling or debouncing if event costs become a concern. [LOW]

Other completed criteria

• Events represent real user actions (story taps, link opens, navigation, filter changes)
• Events enable meaningful product insights — can build story engagement funnels, content depth analysis, scroll engagement trends
• All events include contextual properties (story IDs, titles, types, URLs, comment counts)
• No PII in event properties — usernames (item.by) are public Hacker News handles, not private data
• Event naming is descriptive and uses consistent snake_case convention

---

Reviewed by wizard workbench PR evaluator