vainyala/linkedin-app

Purpose and Entry Points

This is a cross-platform Flutter application for creating and presenting a professional profile/portfolio: user profile, experience, education, skills, certifications, projects, and domain portfolios. The Dart application starts at lib/main.dart; platform launchers host the Flutter runtime on Android, iOS, desktop, and web.

Application Shell and Navigation

The root application in lib/main.dart likely establishes the app shell and initial route. Primary top-level experiences are a dashboard, profile presentation, profile editing, and messaging:

• lib/screens/dashboard_page.dart

• lib/screens/profile_view_page.dart

• lib/screens/edit_profile_page.dart

• lib/screens/MessagePage.dart

Control flows from shell/navigation into screen-specific read/edit operations, rather than through a separate backend service layer visible in the tree.

Profile Domain Model

The app uses explicit Dart models for each profile section. These define the application’s persisted and rendered data boundary:

• lib/models/user_profile.dart

• lib/models/experience.dart

• lib/models/education.dart

• lib/models/skill.dart

• lib/models/certification.dart

• lib/models/project.dart

• lib/models/domain_portfolio.dart

A user profile aggregates or relates to these records; management screens operate on individual collections and profile views compose them into a portfolio.

Local Persistence Boundary

Database access is centralized under lib/database, separating storage representation from UI/model consumers:

• lib/database/database_helper.dart

• lib/database/tables.dart

database_helper.dart is the persistence gateway, while tables.dart defines the schema/table-level contract. Screens and profile composition should depend on this boundary rather than platform-specific storage APIs. No remote API, authentication provider, or cloud service is evident from the supplied repository tree.

Editing and Management Flows

Dedicated management screens provide CRUD-oriented workflows for portfolio sections:

• lib/screens/manage_experience_page.dart

• lib/screens/manage_education_page.dart

• lib/screens/manage_skills_page.dart

• lib/screens/manage_certifications_page.dart

• lib/screens/manage_projects_page.dart

• lib/screens/domain_portfolio_page.dart

The expected flow is: dashboard/profile navigation → edit or manage section → model creation/update → local database helper → refreshed profile/dashboard presentation.

Presentation Composition

Reusable widgets isolate rendering for common profile sections and summary elements:

• lib/widgets/profile_header_widget.dart

• lib/widgets/experience_card.dart

• lib/widgets/education_card.dart

• lib/widgets/certification_card.dart

• lib/widgets/project_card.dart

• lib/widgets/domain_selector_widget.dart

• lib/widgets/stat_widget.dart

These form the UI composition boundary: screen pages coordinate data and interaction, while cards/header/selector render domain-specific fragments. Shared display constants are located in lib/utils/constants.dart.

Runtime and Platform Infrastructure

Flutter/Dart is the shared application runtime. Native host projects package and launch it for Android, iOS, Linux, macOS, Windows, and web:

• Android: android/app/src/main/kotlin/com/example/linked_in/MainActivity.kt

• iOS: ios/Runner/AppDelegate.swift

• macOS: macos/Runner/MainFlutterWindow.swift

• Linux: linux/runner/main.cc

• Windows: windows/runner/main.cpp

• Web: web/index.html

Platform directories are generated/host infrastructure; application behavior is concentrated in lib/.