SPARK / Architecture concept
Many parts.
One engine.
A reusable product engine and the consumer app built on it. This high-level study explores how an interface, shared logic and the state behind them can work as one system.
Tap a node to explore. Drag sideways to pick it up, then move it. With a keyboard, focus a node and use the arrow keys.
The part someone sees and touches. A clear action starts a small, understandable change.
Explore the loop, one step at a time.
A high-level architecture study. The flow is an illustrative local interaction, not a capture of the product or its underlying services.
Static concept preview. JavaScript enables the controls.
Inside the experience
A small action.
A connected response.
The interface is one part of a product. A change also needs a clear meaning, somewhere to keep its context and a useful response for the person who made it.
Pick up the pieces and follow the loop. Their positions can change while the relationships stay connected. The study makes that separation visible.
- The experience
- A touchable view of the parts, with an explanation next to the interaction. The same actions are available from a keyboard.
- The architecture
- An illustrative separation of experience, rules, record and feedback. These are concept roles, not a published technical specification.
- The current scope
- SPARK is an early build. This local concept does not connect to its services, collect data or present an actual product capture.
Working on something with a few moving parts?
Talk through the product