Roadmap (2025) #725
Description
🚀 Inventory Framework Roadmap
Welcome to our official roadmap!
This issue outlines our current priorities, planned features, and long-term goals. Feel free to watch or comment to stay in the loop or contribute ideas. Let’s build something great together!
🟢 Current Goals (Jun/2025–Sep/2025)
The current state of the library is stable. Inventory Framework is used on more than 500 servers around the world with all possible versions and with various types of software supported.
The biggest current goal is to improve documentation, implement features that make sense and simplify the use of the framework. The way Inventory Framework works may be "strange" to many developers, it may seem complex but it is not, that is why it is so important to document as much as possible and write intuitive documentation for using the library.
Documentation is the biggest goal for 2025.
By priority
- Documentation including [RFC] Documentation for Endless Contexts #690
- Refs API Improvements
Refs API is a really useful feature for the way how Inventory Framework works, more than 10 people already requested me (DevNatan) "how do I do..." that would be solved by using Refs API. So Refs API documentation and code improvements is a goal. - Introduce global "on each render" handler #619
- Change computed pagination API design #724
- Pagination orientation #387
- Keyed pagination elements #437
- Timeable out item render #78
🔜 Upcoming (Sep/2025–Dez/2026)
- Custom Components
A way to create custom components, specially useful for creating themed inventories for newest MC versions. - Compose UI
Compose UI is a technology to create user interfaces using Kotlin. We'll provide way to create inventories using Compose UI with Inventory Framework running under the hood.
🧭 Long-Term (2026)
- IntelliJ Tooling Plugin
That is my (DevNatan) personal goal. The objective here is provide a way to preview the inventory while coding it, also, a way to snapshot test.
✅ Completed
💬 Contribute or Suggest
Have ideas? Found bugs? Want to suggest improvements?
Feel free to open an issue or start a discussion here — we’re always happy to collaborate.