3 ms·
What we need before all this is a better way of specifying program behavior, both at a high and a low level. In mobile there are multiple tools that you can us
by manv1 4y ago
What we need before all this is a better way of specifying program behavior, both at a high and a low level.
In mobile there are multiple tools that you can use to prototype UI behavior. They allow you to specify navigation, transitions, clickable areas, behaviors when clicked, swipe actions, etc. They're this way so that the UI behaviors can be seen before coded (to an extent - not every prototyping tool does everything).
For code, well, only formal specifications get to that level. I haven't actually seen one of those outside of software engineering books, but I presume they exist in more critical fields. Commercial software doesn't really use them because they're too much work.
- Taikonerd 4y agoThis Hillel Wayne post [0] mentions a startup called Sketch.systems [1], which I think is sort of like what you said? It's not just a UI prototype; you build a model of the underlying state of the system as you transition from screen to screen. 0: https://www.hillelwayne.com/formally-specifying-uis/ https://www.hillelwayne.com/formally-specifying-uis/ 1: https://sketch.systems/ https://sketch.systems/
- dugmartin 4y agoThere was a lot of money poured into doing this in the 80s and 90s without much success. Maybe it is time to try again? https://en.wikipedia.org/wiki/Fifth-generation_programming_language https://en.wikipedia.org/wiki/Fifth-generation_programming_l...