How johnaljennegalos/parsu-consult works
The tree indicates a Flutter client and a Django REST API for a consultation-related product, but the README is empty and no Dart application code or Django routing/view/model implementation was sampled. The principal user workflow and client-to-API wiring therefore cannot be established. The graph shows only the visible platform startup behavior and the backend components/settings evidenced by the tree and excerpts; backend endpoint relationships are left unconnected rather than assumed.
Main entry points: frontend Flutter application · main.cpp Windows launcher · main.cc Linux launcher · AppDelegate.swift iOS launcher
Components 16
Flutter client startup
- Flutter application
frontend - Windows launcher
frontend/windows/runner/main.cpp - Linux launcher
frontend/linux/runner/main.cc - iOS launcher
frontend/ios/Runner/AppDelegate.swift - macOS window
frontend/macos/Runner/MainFlutterWindow.swift
Django API backend
- Django API
backend/api - Project URL config
backend/core/urls.py - API URL config
backend/api/urls.py - API views
backend/api/views.py - Serializers
backend/api/serializers.py - Permissions
backend/api/permissions.py - API models
backend/api/models.py - SQLite database
backend/core/settings.py - Django settings
backend/core/settings.py - JWT authentication
backend/core/settings.py
Other components
- User
Connections 4
- Windows launcher → Flutter application: starts
- Linux launcher → Flutter application: starts
- iOS launcher → Flutter application: starts
- macOS window → Flutter application: hosts