targetjs

Most modern frameworks model UI as a function of state: change state, re-render. but modern rich UX is increasingly about the space between states. It is about how to represent a smooth transition between states to have a fluid UI. Today, we handle these "in-betweens" state by bolting on external libraries like Framer Motion or GSAP. These often feel like a continuous fight of synching two separate models. I am building TargetJS to experiment with a different model: State as a Destination. In TargetJS, you don't just set a state instead you set a target for the framework to achieve. It treats the journey from state A to B as a first-class citizen. Key Architectural Shifts: - Implicit state and lifecycles: Every class field and function tracks its own progress. - Linear execution: The code executes how it written from top to bottom with n

I have spent over two years figuring out how to solve asynchronous operations in front-end development and provide a unified solution for UI, API loading, animations, state management, and so on. I discovered that it is possible by enhancing the core building blocks which are functions and variables and giving them lifecycles. The result is targets, which also provide unified interface for functions and variables making them equal citizens. Here is an updated version of the framework, available at https://github.com/livetrails/targetjs.

I found out that adding life cycles to methods and variable assignments creates a unified approach to solving UI, animation, state management, event handling, API calls, and more. It also makes development more enjoyable and focused on user experience. Check it out here: https://github.com/livetrails/targetjs I'd love to hear your thoughts