How ravnus-inc/knowme-frontend works
Project type and purpose
• This is a full-stack mobile front-end application built in Flutter, using GetX for state management.
• It’s the client app of “Know Me,” a career management platform that records user activities, interacts with AI analysis, and fetches/postings (jobs, internships, contests) from remote services.
File structure
• Top-level:
• android/ – native Android project
• assets/ – images, svgs, fonts for the UI
• lib/ – all Dart code
– core/ – constants (API URLs), utilities (e.g., storage), theme
– shared/ – reusable API client, shared widgets, shared repositories
– features/ – each feature follows a folder-per-feature pattern (activity, ai_analysis, membership, posts, recommendation, search, home, splash)
– routes/ – app routing definitions
• test/ – unit and widget tests
• Pattern: Presentation (views), State (GetX controllers), Domain (services & repositories), Data (ApiClient), Models in each layer, following a variant of MVVM or layered architecture with the Repository pattern.
README insights
• Confirms use of Flutter, GetX, REST-style APIs.
• Outlines features: login/signup (with OAuth), activity tracking, post recommendation, AI analysis.
1. Mobile App (Flutter Engine)
• Presentation Layer
• UI Screens & Widgets (lib/features/*/views, shared/widgets)
• State Management
• GetX Controllers (lib/features/*/controllers, core/utils/storage_utils for local persistence)
• Domain Layer
• Services (lib/features/*/services, shared/services/api_client.dart)
• Repositories (lib/features/*/repositories, shared/repositories/*)
• Data Layer
• ApiClient (core/utils + shared/services/api_client.dart)
• Local Storage (secure token storage via storage_utils)
2. External Systems
• Authentication & User Profile API
• Posts API (jobs, contests, internships)
• AI Analysis API (analysis & summary)
• Third-party OAuth Providers (Google, Naver)
1. UI → Controller: user taps/clicks
2. Controller → Service/Repository: business logic invocation
3. Repository → ApiClient: HTTP request (with tokens from Local Storage)
4. ApiClient → External API: network call
5. External API → ApiClient → Repository → Controller → UI: data flow back
6. Controller ↔ Local Storage: read/write tokens, cached data
c. Architectural patterns & principles:
• Layered architecture (Presentation → Domain → Data)
• Repository pattern abstracts data sources
• GetX for reactive state management & dependency injection
• Single ApiClient for HTTP concerns (timeouts, headers)
• Feature modularization for scalability
d. Relevant technologies:
• Flutter framework & Dart language
• GetX package (routing, state, DI)
• RESTful APIs over HTTP(S)
• OAuth 2.0 (Google, Naver)
• Local storage (shared_preferences / secure storage via storage_utils)