🎉 apps-state-diagram is now compatible with JetBrains IDE editors! plugins.jetbrains.com/plugin… cc/ @mamund

ALPS now allows you to display only the descriptors for selected tags and share them via URL. cc/ @mamund editor.app-state-diagram.com…

> REST's deepest insight wasn't about HTTP methods or status codes. It was this: separate the what from the how, and unanticipated clients become possible. Fielding designed REST so a server could be written once, and clients that were never imagined at design time could still use it correctly — because the uniform interface made behavior discoverable, not assumed. ALPS inherits exactly that spirit. Define the application semantics once — ontology, taxonomy, choreography — and unanticipated uses of that definition emerge naturally. Nobody designed ALPS specifically to: ・Make wireframes that reveal vocabulary on hover ・Give AI agents a noise-free semantic document to consume ・Double as an accessibility specification ・Drive both a hypermedia API and its HTML frontend from the same profile But all of these fall out naturally — because the profile describes what the application is, not how it's rendered. Just as REST's uniform interface allowed browsers, mobile apps, and IoT devices to consume the same API, ALPS's semantic contract allows designers, developers, AI agents, and screen readers to consume the same structure.