WellNuo/Discussion_Points.txt
Sergei 1e2c2b9856 Full sync with auth screens and discussion docs
Added:
- forgot-password.tsx, register.tsx auth screens
- Discussion_Points.md and Discussion_Points.txt

Updated:
- login, chat, index, beneficiary detail screens
- profile/help and profile/support
- API service
- Scheme files (Discussion, AppStore)

All assets/images are tracked and safe.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-12-12 17:04:46 -08:00

68 lines
2.0 KiB
Plaintext

WELLNUO MOBILE APP
Discussion Points for EluxNetworks Team
────────────────────────────────────────────────────────────
1. BACKEND/API DEVELOPMENT ACCESS
Request: Can I get access to develop backend/API endpoints myself?
Why?
- No fixed technical specification - requirements will change frequently
- Waiting for backend = blocked frontend work = significant delays
- Can't predict all API needs upfront - discovery happens during implementation
Option A: Access Granted (Preferred)
I need:
- Repository access (or separate repo)
- Database documentation
- Architecture overview
I will:
- Implement endpoints myself
- Document all changes
Option B: No Access
EluxNetworks implements these APIs:
- Auth: Registration, Password reset, Email verification
- Billing: Subscription plans, Payments (Stripe)
- Beneficiary: CRUD, Family invites
- Orders: Product catalog, Order tracking
- Notifications: Device registration, Push settings
- Profile: User CRUD, Password change, Account deletion
Important: This list is a rough estimate, not a final specification.
Actual requirements will change during development.
Expect multiple rounds of revisions and delays.
────────────────────────────────────────────────────────────
2. WEBVIEW EMBED MODE
Request: Add ?embedded=true parameter to hide UI elements
Hide:
- Header "Dashboard Details"
- Navigation arrows (< >)
- Logout button
Reason: Mobile app has its own navigation and auth.
────────────────────────────────────────────────────────────
SUMMARY
Backend access = fast development, flexible, minimal delays
Wait for APIs = slow, multiple spec revisions, blocked work
Recommendation: Backend access for fastest delivery.