5737dce4ba
- Updated login screen - Updated chat screen - Updated AuthContext - Updated API service - Updated packages - Updated discussion docs and scheme 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
91 lines
3.0 KiB
Plaintext
91 lines
3.0 KiB
Plaintext
WELLNUO MOBILE APP
|
|
Discussion Points for EluxNetworks Team
|
|
|
|
────────────────────────────────────────────────────────────
|
|
|
|
CURRENT STATUS
|
|
|
|
I've uploaded the latest build to TestFlight. Please test on iOS.
|
|
|
|
Tomorrow I'll start working on Android deployment.
|
|
|
|
We need to schedule a call to discuss these questions in more detail.
|
|
I've hit some bottlenecks and need clarification before moving forward.
|
|
All questions are listed below and in the project scheme.
|
|
|
|
────────────────────────────────────────────────────────────
|
|
|
|
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 access OR database dump (so I can set up my own)
|
|
- 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.
|
|
|
|
|
|
────────────────────────────────────────────────────────────
|
|
|
|
3. ACCOUNT ACCESS NEEDED
|
|
|
|
Apple Developer Account
|
|
- Need access for App Store submissions, certificates, push notifications setup
|
|
|
|
Stripe Account (if we're integrating payments/subscriptions)
|
|
- Need API keys for payment integration
|
|
- Need access to configure products, prices, webhooks
|
|
|
|
────────────────────────────────────────────────────────────
|
|
|
|
SUMMARY
|
|
|
|
Backend access = fast development, flexible, minimal delays
|
|
Wait for APIs = slow, multiple spec revisions, blocked work
|
|
|
|
Recommendation: Backend access for fastest delivery.
|