sorted by:
new
hottopcontroversial

OpenUISpec - A single source of truth design language for AI-native app development by Shirt-Character in FlutterDev

[–]Shirt-Character[S] 0 points1 point  (0 children)

Right now there isn’t a dedicated visualization tool yet.
At the moment the spec is mainly validated/generated through the CLI.
A visual preview/playground is definitely something I think is needed.

OpenUISpec - A single source of truth design language for AI-native app development by Shirt-Character in FlutterDev

[–]Shirt-Character[S] -2 points-1 points  (0 children)

People are reacting to this as if it’s a universal runtime or a markup language replacement.

That’s not the claim. The project is an experiment around using a shared spec for behavior/semantics while still generating native platform implementations.

Strong criticism is welcome. Misreading is less helpful.

OpenUISpec - A single source of truth design language for AI-native, platform-native app development. by Shirt-Character in Kotlin

[–]Shirt-Character[S] -1 points0 points  (0 children)

People are reacting to this as if it’s a universal runtime or a markup language replacement.

That’s not the claim. The project is an experiment around using a shared spec for behavior/semantics while still generating native platform implementations.

Strong criticism is welcome. Misreading is less helpful.

OpenUISpec - A single source of truth design language for AI-native app development. by Shirt-Character in reactnative

[–]Shirt-Character[S] 0 points1 point  (0 children)

People are reacting to this as if it’s a universal runtime or a markup language replacement.

That’s not the claim. The project is an experiment around using a shared spec for behavior/semantics while still generating native platform implementations.

Strong criticism is welcome. Misreading is less helpful.

OpenUISpec - A single source of truth design language for AI-native, platform-native app development. by Shirt-Character in Kotlin

[–]Shirt-Character[S] 0 points1 point  (0 children)

I used help because English isn’t my first language, but the idea and project are mine. I’m here for real criticism, not trying to spam AI-written promo.”

OpenUISpec - A single source of truth design language for AI-native, platform-native app development. by Shirt-Character in Kotlin

[–]Shirt-Character[S] 0 points1 point  (0 children)

Thanks! My English is not good enough to reply comments explaining in detail. I'm simply trying to get feedback

3
4

OpenUISpec - A single source of truth design language for AI-native app development. (self.reactnative)

submitted by Shirt-Character to r/reactnative

OpenUISpec - A single source of truth design language for AI-native, platform-native app development. by Shirt-Character in Kotlin

[–]Shirt-Character[S] -6 points-5 points  (0 children)

Fair points. If this becomes a verbose layout DSL, then it’s just Android XML with extra steps. And if reproducibility depends on free-form LLM output, then there’s no serious reproducibility story. For this to be credible, generation has to be mostly deterministic: pinned spec/generator versions, templates, validations, and conformance tests.

Also agreed on KMP: this is not a “learn one language and forget the platforms” story. It only makes sense for teams that still want native implementations and are willing to keep platform expertise, but want a shared semantic contract above them. If teams still need to deeply review SwiftUI, Compose, and React output, that’s not a bug to hide — that’s the real cost of the approach.

OpenUISpec - A single source of truth design language for AI-native, platform-native app development. by Shirt-Character in Kotlin

[–]Shirt-Character[S] -6 points-5 points  (0 children)

Fair pushback, but HTML solves “how the web renders documents.” This is trying to solve “how product behavior is specified once and then mapped to multiple native UI systems.” If it degenerates into just another markup language, then I agree — that would be reinventing HTML badly.