mcpField
F
feature-flags-android

feature-flags-android

github.com/posthogDevelopment7698 installsUpdated today
Repository

About feature-flags-android

A coding skill for adding PostHog feature flags to Android applications. It provides Android-specific setup guidance and flag practices, including initialization, build configuration, and optional flag management through PostHog MCP tools.

Key features

  1. 01Android-specific setup references
  2. 02Feature flag implementation guidance
  3. 03Environment variables for PostHog keys
  4. 04Gradle dependency configuration guidance
  5. 05PostHog MCP flag management

Use cases

  1. 01Add feature flags to an Android app
  2. 02Initialize PostHog in an Application class
  3. 03Manage flags through connected PostHog MCP tools

MCP support

If a PostHog MCP server is connected, the skill can use its tools to create, list, update, or delete feature flags.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/posthog/skills --skill feature-flags-android

After installing, type/feature-flags-androidin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
adding-feature-flag-code.md
android.md
best-practices.md

Details

From the project README

PostHog feature flags for Android

This skill helps you add PostHog feature flags to Android applications.

Reference files

  • references/android.md - Android feature flags installation - docs
  • references/adding-feature-flag-code.md - Adding feature flag code - docs
  • references/best-practices.md - Feature flag best practices - docs

Consult the documentation for API details and framework-specific patterns.

Key principles

  • Environment variables: Always use environment variables for PostHog keys. Never hardcode them.
  • Minimal changes: Add feature flag code alongside existing logic. Don't replace or restructure existing code.
  • Boolean flags first: Default to boolean flag checks unless the user specifically asks for multivariate flags.
  • Server-side when possible: Prefer server-side flag evaluation to avoid UI flicker.

PostHog MCP tools

Check if a PostHog MCP server is connected. If available, look for tools related to feature flag management (creating, listing, updating, deleting flags). Use these tools to manage flags directly in PostHog rather than requiring the user to do it manually in the dashboard.

Framework guidelines

  • Adapt dependency configuration to the appropriate build.gradle(.kts) file according to the project gradle version
  • Call PostHogAndroid.setup() only once in the Application class's onCreate() method, so it's initialized as early as possible and only once.
  • Initialize PostHog in the Application class's onCreate() method
  • Ensure every activity has a android:label to accurately track screen views.

Comments

Markdown supported