[Kitenite]

Summary

Follow-up to #7611 and #7655 now that the /mobile page is on main. The launch post stays hidden (draft: true).

• Promotes StoreBadges from the mobile page folder to [lang]/components/, since the post now uses it too. It reads the launch flag from MobileLaunchProvider instead of taking an isLaunched prop, and takes a source for analytics plus an androidHref (defaults to #android)
• mobile_store_clicked now carries source: mobile_page from the landing page, blog_superset_mobile from the post, so installs can be attributed to the post
• Registers StoreBadges as a blog MDX component and uses it as the post's first CTA, replacing the untracked markdown link
• Post copy: links to /mobile, uses the region-neutral App Store URL that COMPANY.APP_STORE_URL uses, and makes the Android waitlist link relative (/mobile#android)

Launch-day order matters: enable the mobile-launch flag first, then remove the post's draft: true line. With the flag off the badge in the post reads "Coming soon to App Store".

Test plan

• bun run typecheck, biome, bun test (141 pass), bun run check:i18n (no catalog changes), vale on the post
• Dev server, flag off: /mobile renders unchanged with both badges pointing at #android; the post (draft line removed locally) renders the badges pointing at /mobile#android, links to /mobile, and has no /us/ store URL
• Preview with the flag on: App Store badge is live in both places and the click event carries source

---

Summary by cubic

Shares the store badges between the mobile landing page and the mobile launch post so installs from the post are tracked. The post stays hidden (draft: true).

• Moves StoreBadges to [lang]/components/ and makes it read the launch flag from MobileLaunchProvider instead of an isLaunched prop.
• The badges now accept a source and an androidHref (defaults to #android).
• mobile_store_clicked now reports source: mobile_page on the landing page and blog_superset_mobile on the post.
• Registers StoreBadges as a blog MDX component and replaces the post's untracked CTA markdown link with it.
• Updates the post copy to link to /mobile, use the region-neutral App Store URL, and use a relative Android waitlist link.

Rollout

• Enable the mobile-launch flag before removing the post's draft: true line.
• With the flag off, the post badge shows "Coming soon to App Store".

^{Written for commit 5e44480. Summary will update on new commits.}

Summary by CodeRabbit

• New Features

  • Added reusable App Store and Google Play badges to blog content.
  • Added support for directing Android badge links to a specified destination.
  • Improved mobile app download tracking across supported badge placements.

• Updates

  • Updated mobile download links and requirements text in the mobile app blog post.
  • Standardized app store badge behavior between the mobile page and blog content.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 28ca090c-1dfc-4ecc-86d0-23d7f6be6481

📥 Commits

Reviewing files that changed from the base of the PR and between 5014dec and 5e44480.

📒 Files selected for processing (5)

• apps/marketing/content/blog/superset-mobile.mdx
• apps/marketing/src/app/[lang]/blog/components/mdx-components.tsx
• apps/marketing/src/app/[lang]/components/StoreBadges/StoreBadges.tsx
• apps/marketing/src/app/[lang]/components/StoreBadges/index.ts
• apps/marketing/src/app/[lang]/mobile/page.tsx

Included review availability: Your plan provides up to 10 included reviews per hour; 6 remain after this review.

---

📝 Walkthrough

Walkthrough

The change updates StoreBadges to derive launch state internally and track its source. The mobile page and blog MDX renderer use the new API. The mobile blog content now renders store badges and uses updated store links.

Changes

Mobile Store Badge Integration

Layer / File(s)	Summary
StoreBadges behavior apps/marketing/src/app/[lang]/components/StoreBadges/StoreBadges.tsx	StoreBadges now uses useIsMobileLaunched, requires a source, accepts an optional androidHref, and includes source in App Store click tracking.
StoreBadges consumers and content apps/marketing/src/app/[lang]/blog/components/mdx-components.tsx, apps/marketing/src/app/[lang]/mobile/page.tsx, apps/marketing/content/blog/superset-mobile.mdx	The mobile page and blog MDX renderer use the updated component API. The blog content renders StoreBadges and updates its store and waitlist links.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Feature

Sequence Diagram(s)

sequenceDiagram
  participant BlogMDX
  participant mdxComponents
  participant StoreBadges
  participant MobileLaunchProvider
  BlogMDX->>mdxComponents: render StoreBadges with source and androidHref
  mdxComponents->>StoreBadges: pass component props
  StoreBadges->>MobileLaunchProvider: read mobile launch state
  StoreBadges-->>BlogMDX: render store badges

Loading

Merge Risk: ⚪ Minimal · up to 5e444

The reusable store badges are wired correctly for the mobile page and blog, with no actionable merge-blocking risk identified.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 3 files. (1 skipped: 1 …	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title uses conventional commit format and clearly describes the main change: sharing the store badges with the mobile launch post.
Description check	✅ Passed	The description explains the changes, motivation, rollout order, analytics updates, and test results. It includes testing details and identifies the remaining preview verification. The headings differ…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 3 files. (1 skipped: 1 unsupported.)

• Fix all pre-merge checks with AI

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🧹 Preview Cleanup Complete

The following preview resources have been cleaned up:

• ✅ Neon database branch

Thank you for your contribution! 🎉