How slimeball12399/pivot_expert_in_teams works
Pivot combines a mobile client with Django account services and a web interface. The main verified workflow is mobile sign-in or registration: form hooks validate input, the auth provider invokes API functions, and the API client manages requests and stored tokens. On the server, API views use serializers and account services for account, verification, and profile operations; services use account models and email/verification helpers. Web account flows are also present. The README is empty, and some routing and integration details were not sampled, so uncertain links are omitted or marked unverified.
Main entry points: services.py Account workflows · models.py Account records · web/views.py Web views · api/views.py API views
Components 23
Mobile app
- Auth screen
MobileApp/src/screens/AuthScreen.js - Login form
MobileApp/src/hooks/useLoginForm.js - Registration form
MobileApp/src/hooks/useRegisterForm.js - Auth state
MobileApp/src/providers/AuthProvider.js - Auth API
MobileApp/src/api/auth.js - Request client
MobileApp/src/api/client.js - Secure token store
MobileApp/src/utils/storage.js - Input validation
MobileApp/src/utils/validators.js
Account services
- Account workflows
Server/accounts/services.py - User manager
Server/accounts/manager.py - Account records
Server/accounts/models.py - Account validation
Server/accounts/validators.py - Code verification
Server/accounts/verification.py - Email rendering
Server/accounts/emails.py
HTTP API
- API views
Server/api/views.py - API serializers
Server/api/serializers.py - API errors
Server/api/exceptions.py
Voice utility
- Voice feature extraction
VoiceMock/FeatureExtractor.py
Other components
- App user
- Django API
- Web user
Connections 30
- App user → Auth screen: uses
MobileApp/src/screens/AuthScreen.js - Auth screen → Login form: renders
MobileApp/src/screens/AuthScreen.js - Auth screen → Registration form: renders
MobileApp/src/screens/AuthScreen.js - Login form → Input validation: validates with
MobileApp/src/hooks/useLoginForm.js - Registration form → Input validation: validates with
MobileApp/src/hooks/useRegisterForm.js - Login form → Auth state: calls login
MobileApp/src/hooks/useLoginForm.js - Registration form → Auth state: calls register
MobileApp/src/hooks/useRegisterForm.js - Auth state → Auth API: calls
MobileApp/src/providers/AuthProvider.js - Auth state → Secure token store: reads and writes
MobileApp/src/providers/AuthProvider.js - Auth API → Request client: requests through
MobileApp/src/api/auth.js - Request client → Secure token store: reads and refreshes
MobileApp/src/api/client.js - Request client → Django API: sends HTTP requests
MobileApp/src/api/client.js - Django API → API views: routes requests to
- API views → API serializers: uses
Server/api/views.py - API views → Account workflows: calls
Server/api/views.py - API views → API errors: uses
Server/api/views.py - API serializers → Account records: reads account data
Server/api/serializers.py - API serializers → Account workflows: uses
Server/api/serializers.py - Account workflows → Account records: reads and updates
Server/accounts/services.py - Account workflows → Email rendering: sends mail via
Server/accounts/services.py - Account workflows → Code verification: uses
Server/accounts/services.py - User manager → Account records: creates users
Server/accounts/manager.py - User manager → Account workflows: schedules verification
Server/accounts/manager.py - Account records → User manager: configures
Server/accounts/models.py - Account records → Account validation: validates fields with
Server/accounts/models.py - Web user → Web views: uses
- Web views → Web forms: uses
Server/web/views.py - Web views → Account workflows: calls
Server/web/views.py - Web views → Email rendering: uses
Server/web/views.py - Web views → Account records: reads account data
Server/web/views.py