01 // Beyond Installation
Why Implementation Support
Installing a framework is usually the easy part.
The real integration starts when that framework needs to communicate with the save system, UI, characters, input, networking, scenes, content pipeline, or other project-specific systems.
Framework Implementation is for teams that want to use one of our systems without handling every integration detail internally.
02 // Integration Scope
What we Handle
Connect the framework to the systems around it.
Initial Setup
- Installation
- Package configuration
- Required dependencies
- Initial project setup
- Sample removal or adaptation
Project Integration
- Existing save systems
- Input systems
- UI
- Gameplay systems
- Characters
- Scenes
- Data
- Networking where supported
Extensions
- Custom adapters
- Project-specific APIs
- Additional behaviours
- Custom data
- Workflow extensions
- Editor changes
Handover
- Team guidance
- Technical documentation
- Integration notes
- Usage examples
- Project-specific setup information
03 // Fit the Project
Existing Architecture
Your existing architecture comes first.
Possible Integration Approaches
We do not assume unrelated systems need to be replaced simply because a framework is being introduced.
Before implementation, we review the systems the framework needs to interact with.
Configuration
The framework already supports the requirement and only needs project-specific setup.
Adapter
A lightweight translation layer connects your existing system and the framework.
Extension
The framework is extended through its existing APIs and extension points.
Custom Integration
Project-specific code handles requirements outside the standard implementation.
04 // When more is needed
Custom Development
Standard implementation does not need to solve every project-specific problem.
Clear Boundaries
Sometimes a framework covers most of the requirement while one particular part remains unique to your project.
That additional work can be scoped separately as Engineering Consulting rather than unnecessarily changing the base framework.
Before additional work proceeds, we define:
- What the standard framework already provides
- What is configuration
- What is project-specific integration
- What requires custom development
- Who owns the resulting code
- What remains update-compatible
05 // Framework Integration
Already evaluating one of our Unity frameworks?
Send us the framework name, Unity version, relevant project systems, and what the integration needs to accomplish.