amypellegrini / amypellegrini/jazzjamweb

Support / FAQ page (with IAP purchase, restore, refund guidance)

Open
#38 0 comments 0 reactions 0 assignees View on GitHub
enhancement goal:revenue invest:feature
Dominant language
HTML
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

## Summary

Create a public **Support / FAQ page** on the JazzJam website, covering general app questions and — critically — In-App Purchase topics: how to purchase, how to restore purchases, and refund/cancellation guidance.

## Business Value

App stores require a reachable **support URL** on the listing of any app with paid features. Beyond the compliance need, a public FAQ deflects purchase-related support load (restore purchases, "I paid but don't see it", refunds) and builds buyer confidence before install.

## Scope

### In scope
- A support/FAQ page reachable from the site navigation
- IAP section: how to buy Pro Unlock, how to restore purchases, refund/cancellation policy pointers, "purchased but not unlocked" troubleshooting
- General app FAQ entries
- A contact/support route (email or form)

### Out of scope
- TOS and Privacy Policy content — covered by #16
- In-app help/onboarding (app repo)

## Acceptance Criteria

- [ ] Support/FAQ page exists and is linked from site navigation
- [ ] Page includes an IAP section covering purchase, restore, and refund/cancellation
- [ ] A working contact/support route is present
- [ ] Page renders correctly on desktop, tablet, and mobile

## Manual Verification

1. From the site navigation, open the Support/FAQ page — confirm it loads
2. Locate the IAP section — confirm purchase, restore-purchases, and refund/cancellation guidance are present
3. Use the contact/support route — confirm it works (email opens / form submits)
4. Confirm the page URL is suitable for use as the store listing's support URL

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.