social.plus UIKit offers three levels of customization to match your needs. Choose the right approach based on how much control you need over the user interface.Documentation Index
Fetch the complete documentation index at: https://learn.social.plus/llms.txt
Use this file to discover all available pages before exploring further.
Choose Your Customization Level
Dynamic UI
Minimal Customization
- Colors, text, and basic styling
- No code changes required
- Perfect for brand consistency
- Real-time updates without app releases
Component Styling
Moderate Customization
- Custom CSS and styling overrides
- Advanced theming options
- Component-level modifications
- Still within UIKit framework
Fork & Extend
Advanced Customization
- Complete control over components
- Custom layouts and workflows
- Maintain your own version
- Jumpstart for complex projects
Start simple and scale up: Begin with Dynamic UI for quick brand consistency, move to Component Styling for deeper control, or Fork & Extend when you need complete customization freedom.
Level 1: Dynamic UI - Minimal Cacheustomization
Perfect for teams who want to quickly customize colors, text, and basic styling without writing any code.Configuration-Based
Single config.json File
- Centralized customization
- Light and dark themes
- Brand colors and typography
- No app updates required
Real-time Updates
Live Configuration
- Instant theme switching
- A/B testing capabilities
- Remote configuration
- Version control friendly
Level 2: Component Styling - Moderate Customization
For teams who need deeper styling control while staying within the UIKit framework.Advanced Theming
CSS & Style Overrides
- Custom stylesheets
- Component-specific styling
- Advanced color schemes
- Typography control
Component Control
Granular Customization
- Individual component styling
- Page-specific themes
- Element-level customization
- Conditional styling
Level 3: Fork & Extend - Advanced Customization
For teams who need complete control over components and user flows.Complete Control
Fork GitHub Repository
- Access to full source code
- Modify any component or workflow
- Custom layouts and interactions
- Unlimited customization freedom
Maintain Your Version
Full Ownership
- Your own codebase
- Custom feature development
- Integration with existing systems
- Professional development workflow
When to Fork & Extend
Consider forking when you need:- Custom user flows that donβt exist in UIKit
- Integration with complex existing systems
- Unique layouts that canβt be achieved with styling
- Complete control over the development roadmap
Decision Matrix
| Goal / Constraint | Dynamic UI | Component Styling | Fork & Extend |
|---|---|---|---|
| Rebrand colors quickly | β | β | Overkill |
| Per-component styling | β | β | β (more cost) |
| New flow / navigation paradigm | β | β οΈ Limited | β |
| Replace data layer / inject custom services | β | β | β |
| Deep performance tuning / virtualization changes | β | β | β |
| Add brand-new primitive (e.g. Custom feed) | β | β | β |
| Minimal maintenance capacity | β | β | β |
Taxonomy: Elements β Components β Pages
UI Elements (Atoms)
UI Elements (Atoms)
Primitive building blocks (buttons, text, avatar). Light logic. Style mostly via tokens; rarely stateful beyond hover / active / disabled.
Components (Presentational vs Controller)
Components (Presentational vs Controller)
Presentational: Compose elements; focus on layout / visuals.
Controller: Contain orchestration logic (e.g. data fetch, pagination). Examples:
Controller: Contain orchestration logic (e.g. data fetch, pagination). Examples:
FeedList, PostView.Pages (Screens)
Pages (Screens)
Route-level surfaces combining multiple controller/components with navigation context.
Need Help with Customization?Our design team is available to help you create the perfect look for your app. Contact our customization experts for personalized assistance.