How tarikulker-js/ulker-social-v2 works
Project type and purpose
• This is a cross-platform Flutter application (“ulkersocialv2”), targeting Android, iOS, Linux, macOS, Windows and Web.
• From the lib/ folder and file names (screens, components, middleware, storage), it’s clearly a client-side social-style app—handles UI pages (login, feed, profile, chat), local token storage, date conversion, and likely talks to remote APIs for posts, reels, comments, likes, etc.
File structure
• Top-level platform folders (android/, ios/, linux/, macos/, windows/, web/) contain Flutter engine embedding and native glue.
• lib/ subdivides into:
• components/ – reusable UI widgets.
• screens/ – full-page layouts (LoginScreen, ExploreScreen, ChatScreen, etc.).
• middleware/ – pure-Dart utilities/business logic (e.g., ConvertDateToAgo).
• storage/ – local persistence (SecureStorage).
• main.dart – app entry point (sets up routing, DI, theme).
• pubspec.yaml defines dependencies; test/ holds widget tests.
README
• It’s the default Flutter starter README, confirming this is a front-end project. No mention of backend code here, so assume “external API(s)” for data.
Detail & essential architectural elements
• Don’t omit the main.dart/router component that wires up screens and services.
• Screen category (Home, Explore, Chat, Profile, Reels) as sub-components under the Presentation layer.
• Middleware utilities (e.g., ConvertDateToAgo, CheckToken) as distinct nodes.
• SecureStorage separately from in-memory state.
• Native runners (android/ios/etc.) under a “Platform Embedders” container feeding into the Flutter runtime.