Tadrisino/MathApp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

CLAUDE.md: pointer to the next-APK notes and why app payments go through pay.html

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Zareian
2026-10-10 18:54:12 +03:30
parent 9024c6b8d8
commit 4821df3914
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
CLAUDE.md
View File

@@ -191,6 +191,12 @@ of `PATCH` on notifications, a dropped guest refresh token). Read the contract f
`python manage.py spectacular --file schema.yaml --format openapi` and check shapes `python manage.py spectacular --file schema.yaml --format openapi` and check shapes
against a running server. `content/tests_frontend_contract.py` is the backend-side guard. against a running server. `content/tests_frontend_contract.py` is the backend-side guard.
**Android app (WebView shell in the frontend repo, `android/`):** the installed APK lags the code. What the
next build must carry (vibrate bridge, in-app Zarinpal with `paysInApp()`, media-gesture setting), what to
check on a phone, and who owns signing (MH-W90) are in `~/Desktop/MathApp_frontend/android/README.md`
(«نسخه‌ی بعدیِ APK»). Until then payment from the app goes through the frontend's `pay.html`, because
Zarinpal refuses StartPay without our domain as Referer (checked live 2026-10-10).
**Content the frontend shows but nobody has filled in yet:** `Unit.blurb`, **Content the frontend shows but nobody has filled in yet:** `Unit.blurb`,
`Plan.features`/`badge`, `Lesson.example`/`steps`. All optional, all editable from the `Plan.features`/`badge`, `Lesson.example`/`steps`. All optional, all editable from the
admin panel. admin panel.