All

Skill 177 of 200

Feature Flags Android

PostHog feature flags for Android applications

1 minute · 201 words · 5 sections

Install

$ npx skills add PostHog/skills --skill feature-flags-android

$ npx skills add PostHog/skills

» /plugin marketplace add PostHog/skills

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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.

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.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/PostHog/skills, branch main, last pushed 24 September 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

200 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 2 distinct layouts observed: skills/omnibus/*/SKILL.md, skills/posthog/all/skills/*/SKILL.md.

Issue colours

Resolved from the awesome-design-md registry — hue 38°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Typefaces

Display: IBM Plex Sans Variable is not a face we ship; the reader's own choice is used.
Body: IBM Plex Sans Variable is not a face we ship; the reader's own choice is used.
Mono: Source Code Pro is not a face we ship; the reader's own choice is used.

We never load a typeface at request time from a third-party origin, so a brand face we do not already self-host is substituted rather than fetched.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “5 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

7 editorial notes across 7 of 200 skills. They are printed in the margin of each skill rather than as errors here.

Signals Scout General — 1 note
Signals Scout PR Follow Up — 1 note
Signals Scout Product Analytics — 1 note
Signals Scout Replay Vision — 1 note
Signals Scout Skills Store — 1 note
Signals Scout Tasks — 1 note
Signals Scout Web Analytics — 1 note

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by PostHog, declaring 6 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /PostHog/skills.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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

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.

Feature Flags Android

PostHog feature flags for Android

Reference files

Key principles

PostHog MCP tools

Framework guidelines

Colophon

Feature Flags Android

PostHog feature flags for Android

Reference files

Key principles

PostHog MCP tools

Framework guidelines

Appendix 177.1–177.3

ReferencesMarkdown · 3 files

Colophon

Appendix 177.1–177.3

ReferencesMarkdown · 3 files