Why we have been quiet
It has been almost two weeks since our last development update. That does not mean development has slowed down or stopped. We have deliberately chosen not to publish…
It has been almost two weeks since our last development update.
That does not mean development has slowed down or stopped. We have deliberately chosen not to publish another update while we are still working on the same underlying foundation. During the development of Spixor, the public website has received many visual, interactive and technical improvements.
Individual sections, animations and product experiences have continued to evolve, but the underlying code has also become more complex over time. At a certain point, continuing to make isolated fixes is no longer the right approach. We therefore decided to step back and review how the complete public website currently works.
We are examining its animations, visual layers, scrolling behaviour, performance, code ownership and overall file structure. The next phase is not limited to fixing one animation or one visual issue. We are preparing to rebuild the underlying motion and presentation systems on a cleaner foundation, while reorganizing the public codebase into clearer and more maintainable parts.
This work includes:
This type of work is less visible than launching a new feature, but it is important for everything that comes afterwards. We do not want to keep publishing updates that repeat the same message or show another temporary adjustment. We would rather return with progress that is meaningful, stable and ready to demonstrate honestly. Spixor is still being developed actively. For now, much of that progress is happening beneath the surface. We will share the next update when the renewed foundation is ready to show.
That does not mean development has slowed down or stopped. We have deliberately chosen not to publish another update while we are still working on the same underlying foundation. During the development of Spixor, the public website has received many visual, interactive and technical improvements.
Individual sections, animations and product experiences have continued to evolve, but the underlying code has also become more complex over time. At a certain point, continuing to make isolated fixes is no longer the right approach. We therefore decided to step back and review how the complete public website currently works.
We are examining its animations, visual layers, scrolling behaviour, performance, code ownership and overall file structure. The next phase is not limited to fixing one animation or one visual issue. We are preparing to rebuild the underlying motion and presentation systems on a cleaner foundation, while reorganizing the public codebase into clearer and more maintainable parts.
This work includes:
- identifying which behaviour is genuinely necessary;
- simplifying overlapping animation and visual systems; • improving performance and runtime stability;
- restructuring large shared files into clearer responsibilities;
- reviewing unnecessary, outdated or duplicated project files;
- preserving the parts of the Spixor experience that already work well.
This type of work is less visible than launching a new feature, but it is important for everything that comes afterwards. We do not want to keep publishing updates that repeat the same message or show another temporary adjustment. We would rather return with progress that is meaningful, stable and ready to demonstrate honestly. Spixor is still being developed actively. For now, much of that progress is happening beneath the surface. We will share the next update when the renewed foundation is ready to show.