t1k:unity:tof:user-experience
| Field | Value |
|---|---|
| Module | tof |
| Version | 2.2.2 |
| Effort | medium |
| Tools | — |
Keywords: scriptable-object, user-experience, ux-service
How to invoke
Section titled “How to invoke”/t1k:unity:tof:user-experienceUser Experience
Section titled “User Experience”Purpose
Section titled “Purpose”Governs home-flow routing and show-condition logic via IUserExperienceService, controlling which UI screens are visible at session start.
Public API
Section titled “Public API”interface
IHomeFlowHandler(IHomeFlowHandler.cs)IShouldGoHome(IShouldGoHome.cs)IShouldGoHomeService(IShouldGoHomeService.cs)IUserExperienceService(IUserExperienceService.cs) classDefaultUserExperienceValue(DefaultUserExperienceValue.cs)DefaultValidate(DefaultValidate.cs)HomeFlowHandler(HomeFlowHandler.cs)ShouldGoHomeService(ShouldGoHomeService.cs)ShouldShowComponent(ShouldShowComponent.cs)UserExperienceConfigKey(UserExperienceConfigKey.cs)UserExperienceLocalData(UserExperienceLocalData.cs)UserExperienceService(UserExperienceService.cs)UserExperienceValidator(UserExperienceValidator.cs)UserExperienceValueToolModule(UserExperienceValueToolModule.cs)UserExperienceVContainer(UserExperienceVContainer.cs)
Signals / Events
Section titled “Signals / Events”None detected.
Config / ScriptableObjects
Section titled “Config / ScriptableObjects”DefaultUserExperienceValue
Integration Steps
Section titled “Integration Steps”- Reference package
TheOneFeaturein your project. - Register the User Experience services via VContainer (see Architecture).
- Configure any ScriptableObjects listed in Config section.
- Subscribe to signals listed in Signals / Events to react to state changes.
Architecture
Section titled “Architecture”Detected public types (15): interface
IHomeFlowHandler(IHomeFlowHandler.cs)IShouldGoHome(IShouldGoHome.cs)IShouldGoHomeService(IShouldGoHomeService.cs)IUserExperienceService(IUserExperienceService.cs) classDefaultUserExperienceValue(DefaultUserExperienceValue.cs)DefaultValidate(DefaultValidate.cs)HomeFlowHandler(HomeFlowHandler.cs)ShouldGoHomeService(ShouldGoHomeService.cs)ShouldShowComponent(ShouldShowComponent.cs)UserExperienceConfigKey(UserExperienceConfigKey.cs)UserExperienceLocalData(UserExperienceLocalData.cs)UserExperienceService(UserExperienceService.cs)UserExperienceValidator(UserExperienceValidator.cs)UserExperienceValueToolModule(UserExperienceValueToolModule.cs)UserExperienceVContainer(UserExperienceVContainer.cs)
Detected DI registrations:
HomeFlowHandlerShouldGoHomeServiceUserExperienceService
Dependencies
Section titled “Dependencies”Run with FEATURE_MATRIX/DEPENDENCY_GRAPH integration to fill.
Gotchas
Section titled “Gotchas”(None reported yet — open an issue in The1Studio/theonekit-unity if you hit one.)
References
Section titled “References”- Source:
UnityTheOneFeatureProject/Packages/TheOneFeature/Core/Features/UserExperience/ - Doc:
UnityTheOneFeatureProject/Packages/TheOneFeature/Core/Features/UserExperience/Core/README.md - Doc:
UnityTheOneFeatureProject/Packages/TheOneFeature/Core/Features/UserExperience/DefaultImplement/README.md - Doc:
UnityTheOneFeatureProject/Packages/TheOneFeature/Core/Features/UserExperience/DefaultImplement/SHOWCONDITON_USAGE.md - Doc:
UnityTheOneFeatureProject/Packages/TheOneFeature/Core/Features/UserExperience/Core/CHANGELOG.md - Doc:
UnityTheOneFeatureProject/Packages/TheOneFeature/Core/Features/UserExperience/DefaultImplement/CHANGELOG.md - Namespace:
TheOne.Features.UserExperience.Core.Components,TheOne.Features.UserExperience.Core.Models,TheOne.Features.UserExperience.Core.Services,TheOne.Features.UserExperience.DefaultImplement.DI,TheOne.Features.UserExperience.Editor,TheOne.Features.UserExperience.DefaultImplement.Models,TheOne.Features.UserExperience.DefaultImplement.Services