frontend-services

To share frontend service logic across React views, you move shared behavior into service modules using module-level singleton getters and register React providers via app.registerProviders() for shared reactive state that triggers re-renders.

The best way to structure frontend services for GraphQL orchestration is by centralizing logic into testable service modules that compose queries, cache results cross-view, and consume the framework's getGraphQLClient() singleton.

To access app context and config services inside non-React frontend callbacks, use the framework singleton access methods getContext() and getConfigService() directly within your lifecycle code and service modules.

Use singleton getters for frontend service classes instead of direct instantiation to ensure lazy module-level initialization, which keeps shared state consistent and makes your application logic highly testable.

Use React context providers with app.registerProviders() when shared reactive state must trigger component re-renders across views; use module-level singletons for non-reactive service logic, GraphQL orchestration, and lifecycle code.

Yes, you can extend frontend service behavior at runtime by defining runtime extension points within views, callbacks, and lifecycle code, while safely consuming framework singletons for app context and configuration.