How gbrlcoelho/nubbleapp works
Project Type & Purpose
• Full-stack (client-only) mobile application built with React Native + TypeScript.
• Acts as a social networking client: handles authentication, profile, feed browsing, posting, likes/comments, follow/unfollow.
• No backend code here; all data operations go through remote REST APIs via domain-layer adapters.
High-Level File-Structure Analysis
• Top-level: configuration (.gitignore, ESLint, Prettier, tsconfig), platform folders (android, ios), entry points (index.js, App.tsx).
• src/ folder subdivided into:
– components (reusable UI primitives & compound widgets)
– screens (feature screens organized by flow: auth, onboarding, app)
– routes (navigation stacks & routers)
– domain (business logic: adapters, APIs, services, use cases)
– services (cross-cutting concerns: authCredentials, multimedia, notifications, permissions, storage, toast, settings, searchHistory)
– infra (generic hooks and infra-level abstractions)
– theme & form & utils & types
– test (unit & integration mocks/servers)
Key Architectural Patterns
• Layered (Presentation → Domain → Infrastructure → External Services)
• Clean Architecture / use-case driven: domain/useCases expose hooks that UI consumes.
• Decorator/Adapter pattern: each domain entity (Auth, Post, User…) has adapter → api layer → service → useCases.
• React Context & Providers for cross-cutting services (AuthCredentialsProvider, ToastProvider).
• React Navigation for routing (stack/tab).
Main Components & Interactions
A. Presentation Layer
– Screens (src/screens/*)
– Shared Components (src/components/*)
– Form/Validation (src/form)
– Navigation (src/routes: AppStack, AuthStack, OnboardingStack)
B. Domain Layer
– Adapters (src/domain/*/*Adapter.ts) transform domain calls to HTTP calls.
– API modules (src/domain/*/*Api.ts) define HTTP endpoints/configs.
– Services (src/domain/*/*Service.ts) orchestrate domain logic.
– UseCases (src/domain/*/useCases/useXYZ.ts) expose business operations.
C. Infrastructure Layer
– apiAdapter & apiConfig (src/api) for HTTP client setup (Axios/fetch).
– Generic hooks (usePaginatedList, useMutation) in src/infra/hooks.
– Local storage implementations (MMKV, AsyncStorage) under services/storage.
– Context Providers (AuthCredentialsProvider, ToastProvider).
D. External Services
– Remote REST API server
– Device APIs: Camera, Permissions
– Push Notifications
– Local Storage
– Third-party libraries (@shopify/restyle for styling)
Data Flow & Relationships
• User interacts with UI (Screen components) → triggers a useCase hook.
• useCase calls domainService → which uses domainAdapter → apiAdapter → HTTP call to external API.
• Response propagates back: API → adapter → service → useCase → UI.
• UI updates state, re-renders components.
• Cross-cutting services (toast, auth credentials, settings) run via React Context.
• Navigation flows between stacks (Onboarding → Auth → App).
Essential Elements Checklist
[ ] Presentation Layer: Screens, Components, Navigation
[ ] Domain Layer: Adapters, APIs, Services, UseCases
[ ] Infrastructure: HTTP client, Storage, Context Providers, Hooks
[ ] External: API server, Device features, Third-party services