pratiknator44/spawnhouse

Purpose and runtime

This is an Angular single-page client for a social/gaming-oriented product: authentication, profiles, feeds/posts, messaging, notifications, “around you,” and now-playing media/game activity. It runs in the browser, with PWA/service-worker support configured by spawnhouse-ui/ngsw-config.json.

Bootstrap and application shell

Angular bootstraps from spawnhouse-ui/src/main.ts into the root module and shell:

• spawnhouse-ui/src/app/app.module.ts

• spawnhouse-ui/src/app/app.component.ts

• spawnhouse-ui/src/app/app.component.html

The shell is the cross-feature composition boundary, likely hosting routed content plus persistent UI such as navigation, overlays, notifications, and now-playing docks.

Routing, feature boundaries, and access control

Route selection is centralized in spawnhouse-ui/src/app/app-routing.module.ts. Feature-specific Angular modules partition major screens:

• spawnhouse-ui/src/app/modules/home.module.ts

• spawnhouse-ui/src/app/modules/profile.module.ts

• spawnhouse-ui/src/app/modules/messaging.module.ts

Navigation is guarded at route boundaries through services including spawnhouse-ui/src/assets/services/login-guard.service.ts, spawnhouse-ui/src/assets/services/profile-guard.service.ts, and spawnhouse-ui/src/assets/services/wildcard-guard.service.ts. Login, password reset, profile management/viewing, and a not-found route are distinct entry states.

Backend API, identity, and local state

spawnhouse-ui/src/assets/services/api.service.ts is the principal HTTP boundary to backend APIs, with endpoint/environment constants under spawnhouse-ui/src/assets/variables/api-vars.enum.ts and spawnhouse-ui/src/environments/environment.ts. spawnhouse-ui/src/assets/services/interceptors.ts centrally modifies HTTP traffic, likely for authentication or common error handling.

Identity and client persistence flow through:

• spawnhouse-ui/src/assets/services/user.service.ts

• spawnhouse-ui/src/assets/services/storage.service.ts

• spawnhouse-ui/src/assets/interfaces/user.interface.ts

UI features should consume these services rather than directly coupling to API/storage details.

Social content and discovery flows

The feed/domain presentation layer is centered on home, feeds, post creation, post viewing, and profile surfaces:

• spawnhouse-ui/src/app/home/home.component.ts

• spawnhouse-ui/src/app/feeds/feeds.component.ts

• spawnhouse-ui/src/app/post-maker/post-maker.component.ts

A typical flow is authenticated user state → API retrieval/mutation → feed/profile component rendering. Discovery and social matching are represented by spawnhouse-ui/src/app/aroundyou/aroundyou.component.ts, suggestions, and reusable user-card display.

Real-time messaging and notifications

Real-time transport is isolated behind spawnhouse-ui/src/assets/services/socket.service.ts and spawnhouse-ui/src/assets/services/get-serverside-event.service.ts; their events feed messaging and notification UI:

• spawnhouse-ui/src/app/messaging/messaging.component.ts

• spawnhouse-ui/src/app/notifications/notifications.component.ts

• spawnhouse-ui/src/app/all-notifications/all-notifications.component.ts

Floating/toast notifications are mediated by spawnhouse-ui/src/assets/services/float-notification.service.ts, separating inbound event handling from transient visual delivery.

Now-playing, overlays, and shared UI state

Now-playing is a cross-cutting stateful feature managed through spawnhouse-ui/src/assets/services/now-playing.service.ts and rendered in primary and docked forms:

• spawnhouse-ui/src/app/now-playing/now-playing.component.ts

• spawnhouse-ui/src/app/now-playing-side-dock/now-playing-side-dock.component.ts

Overlay and navigation visibility are similarly service-mediated (spawnhouse-ui/src/assets/services/overlay.service.ts, spawnhouse-ui/src/assets/services/navbar.service.ts) so routed pages can control global UI without direct shell coupling. Reusable modals, dialogs, image upload, chips, and form widgets compose feature screens.