Hello,
I would like to sincerely share my thoughts and suggestions about Spine.
First of all, I would like to sincerely thank the Spine team for their hard work and dedication. When I purchased Spine, I honestly did not expect to be able to interact so actively with the developers directly through the forum. However, as I read through the forum topics, seeing that the Spine team closely follows and responds to almost every discussion truly impressed me.
This approach makes Spine users feel special and helps them build a strong connection with the software. It creates a feeling among users that “Spine is my program; it grows together with me, I am part of this process, and we are a family.” I believe this is a very valuable feeling. The fact that users can directly contribute to Spine’s development through their suggestions and requests further strengthens this bond.
I have used many different programs so far, but I have never embraced any of them as much as Spine. Compared to other software I have used throughout my life, Spine’s interface is extremely clean, clear, and user-friendly. Of course, there may be aspects that can be improved, but I genuinely like the current interface. For me, I can say that “using Spine is a privilege,” and I sincerely hope that this sense of privilege is preserved. I do not want to say, “this feature exists in other competing programs in this segment, but not in Spine,” especially when those features could add value. That is why I always follow new and exciting updates with great interest.
I believe that the reason users frequently ask for updates is the joy of witnessing Spine’s development step by step. Each new improvement strengthens the feeling that “something is happening” and creates a lively, dynamic connection between users and the project. This is not just about following a product; it is about witnessing growth and being part of it. I truly believe that this bond has been formed.
With your permission, I would like to share a few suggestions and observations. Even if only on a small scale, I read articles and writings related to this industry. I would like to share some points that caught my attention and that I took notes on.
Note 1:
Before purchasing Spine, while researching different software, I came across a program called DragonBones. If I remember correctly, it had a structure similar to Spine. Later, I read that it had not received updates for a long time. As far as I understand, it evolved in a different direction under the name LoongBones and adopted a web-based, AI- supported structure.
Within this AI support, features such as:
• Animation creation via prompts
• Smart bone placement
are said to be provided. I do not know how stable or reliable this system is, but even if it is imperfect, it gives the impression that a basic structure can be created with AI up to a certain point, and then refined through manual adjustments. How efficient this approach is, of course, open to discussion.
Artificial intelligence has now entered many fields. Personally, I prefer AI to be used only as a reference tool. I would like to share a realistic concern: while AI is welcomed positively in many areas, it has also caused serious contractions and transformations in some professions. What makes me uneasy is this: while others benefit from AI at this stage, the idea of Spine falling behind in this regard would not sit well with me.
I have read and am aware that the Spine team is not currently considering AI integration. However, I think it would be very valuable to clearly address the following question: Will AI truly enter the domain of software like Spine in the long term? Or will this area remain outside AI’s reach because Spine focuses more on data rather than visual generation? (I am personally affected by AI in this sense; I sincerely hope it never enters this field. )
Note 2:
I do not have very deep knowledge on this topic, but I did some brief research. I noticed that Unity has created certain internal plugin and extension structures. I think that systems composed of independent plugins such as Timeflow, Magica Cloth 2, Puppet 2D, and Burst Compiler are, in some respects, structured in a way similar to Spine’s approach.
Related video:
VIDEO
As far as I understand, Unity’s physics engine is actively used within this structure. Spine also has its own physics system, but there are some differences between them. For example, in Unity, a character’s hair defined with the physics engine can be automatically affected by external forces. While the hair naturally moves in windy conditions, it can also be influenced organically by a sudden event such as an explosion. I wonder whether a similar approach could be integrated into Spine’s physics system.
I am sure the Spine team has already thought about these topics, and perhaps they may even be tired of hearing about them. If so, I apologize in advance. My only intention was to contribute to a small brainstorming process.
Finally, I would like to sincerely state this: at this stage, I can say that “using Spine is a privilege,” and I want to continue saying this for a long time. I believe that Spine will not make its users feel left behind. Spine already holds a unique position on its own; however, based on my observations, a large portion of users expect new features that will further strengthen this sense of “privilege” and make Spine even more distinctive. I am not pointing these out as shortcomings; on the contrary, I wanted to offer even a small piece of feedback to help Spine become even better.
Thank you very much for taking the time to read this.