docs: update FAQs for Apple restrictions, web-only flows, and Android…

[thinal12]

• App Store publishing: clarified web-only flow with Deploy button, added Expo Launch project setup and Apple Developer sign-in steps.
• Download Code: replaced mobile long-press with web-only flow using the <> button and email download link.
• Android: updated to reflect the app is now available on the Play Store, noted Play Store submission is not yet supported

---

Note

Low Risk
Low risk documentation-only updates; the main risk is user confusion if the described web-only flows or Android capabilities are inaccurate.

Overview
Updates faqs.mdx to reflect current platform support and Apple constraints.

The Android FAQ now states the app is available on Google Play (with no Play Store submission yet). The App Store publishing and code export FAQs are rewritten to explicitly be web-only, with updated step-by-step instructions (Deploy button / <> download flow) and prior mobile instructions commented out.

^{Reviewed by Cursor Bugbot for commit 0fed8a4. Bugbot is set up for automated code reviews on this repo. Configure here.}

Greptile Summary

This PR updates faqs.mdx to reflect that the Android app is now live on Google Play, and rewrites the App Store publishing and code-download FAQs to be explicitly web-only due to Apple restrictions, with updated step-by-step instructions and prior mobile steps commented out. The changes are accurate and clear, but the "What is Vibecode?" opener still describes the product as iOS-and-web-only, which is now inconsistent with the Android launch announced in this same PR.

Confidence Score: 5/5

Safe to merge; documentation-only changes with no runtime impact and only minor content consistency issues.

All findings are P2 style/consistency suggestions. The core content updates (Android availability, web-only flows) are accurate and well-structured. No correctness, security, or data-integrity concerns.

faqs.mdx — the "What is Vibecode?" opener should be updated to mention Android.

Important Files Changed

Filename	Overview
faqs.mdx	Documentation-only update adding Android availability, web-only App Store/download flows, and commenting out old mobile instructions; minor inconsistency in the "What is Vibecode?" opener which still omits Android.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User wants to publish / download code] --> B{Which platform?}
    B -->|Web app| C[App Store: Click Deploy → Deploy to App Store]
    B -->|Web app| D[Download: Click <> → Download Code]
    B -->|iOS mobile app| E[Web-only — not supported on mobile due to Apple restrictions]
    C --> F[Follow wizard → Expo Launch → Apple Developer sign-in]
    D --> G[Download link sent to email]
    F --> H[App submitted to App Store]
    G --> I[React Native/Expo project downloaded]

Loading

Comments Outside Diff (1)

1. faqs.mdx, line 12 (link)

   "What is Vibecode?" accordion still omits Android

   The opening FAQ describes Vibecode as "Available on iOS and on the web at vibecodeapp.com," but this PR now states the Android app is live on Google Play. That description is now stale and could confuse users who arrive at the FAQ page.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: faqs.mdx
   Line: 12
   
   Comment:
   **"What is Vibecode?" accordion still omits Android**
   
   The opening FAQ describes Vibecode as "Available on iOS and on the web at vibecodeapp.com," but this PR now states the Android app is live on Google Play. That description is now stale and could confuse users who arrive at the FAQ page.
   
   
   
   How can I resolve this? If you propose a fix, please make it concise.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: faqs.mdx
Line: 12

Comment:
**"What is Vibecode?" accordion still omits Android**

The opening FAQ describes Vibecode as "Available on iOS and on the web at vibecodeapp.com," but this PR now states the Android app is live on Google Play. That description is now stale and could confuse users who arrive at the FAQ page.

```suggestion
    Vibecode is the easiest way to build apps using natural language. Available on iOS, Android, and on the web at vibecodeapp.com, you can generate fully functional apps with prompting, test them in real-time, and share with anyone instantly.
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: faqs.mdx
Line: 107-111

Comment:
**Commented-out content left in source**

The old mobile instructions are kept as `{/* ... */}` JSX comments rather than removed. While they don't render, they add maintenance noise — future editors may not know whether these are intentionally preserved or simply forgotten. If the mobile flow is permanently retired, removing these blocks would keep the source clean.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "docs: update FAQs for Apple restrictions..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

_{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
vibecode	🟢 Ready	View Preview	Apr 9, 2026, 10:34 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.