IntentForm

Note: This analysis is based entirely on self-reported information from the project description and submission. No external verification, traction data, revenue figures, or customer feedback are available.

The description states that IntentForm:

• Uses a "Semantic Interface Graph" as the source of truth.
• Stores layout meaning, tokens, components, states, flows, accessibility intent, and device behavior in one validated graph.
• Generates deterministic output for Web, React, Expo, and SwiftUI platforms.
• Has three connected workspaces: Design, Code, and Verify.
• Allows inspection of platform-specific outputs and connection to the original graph nodes.
• Includes a Judge Mode for reviewers to inspect intent, compare outputs, and test repair workflows.
• Is open-source with hosted versions available.

Inference: The tool appears to be a developer-facing system designed to manage cross-platform UI consistency via semantic representation, not just code generation.

Claim: The product keeps product intent as the source of truth.

Evidence: Stated in the write-up.

Inference: It uses AI tools (Codex, GPT 5.6) for development and decision-making.

Evidence: Author reports using Codex from idea to release, including planning, architecture, implementation, testing, and documentation.

The author positions IntentForm as:

• A solution to the problem of inconsistent product decisions across platforms.
• Inspired by Figma and Paper — tools that make visual work feel direct and easy to understand.
• Designed to ensure that "product intent can also compile, run and prove itself".
• Not just about generating code quickly but maintaining meaning behind it.

Inference: IntentForm is positioned as a tool for developers who want to maintain control over product decisions while leveraging automation.

Claim: One product decision should not become four platform rewrites.

Evidence: Stated in the write-up.

Claim: Generated code is not proof that a product still follows the original decision.

Evidence: Stated in the write-up.

The description does not clearly identify a specific customer segment or ideal customer profile (ICP). It mentions:

• Developers working with multiple platforms.
• Teams needing to ensure consistency across Web, React, Expo, and SwiftUI.
• Reviewers who can inspect intent and verify results in Judge Mode.

Inference: The primary users are likely developers or product teams managing multi-platform UIs, though no explicit targeting is made.

Claim: IntentForm targets teams that want to avoid rewriting the same product decision across platforms.

Evidence: Stated in the write-up.

Claim: It's for people who value inspectability and traceability of changes.

Evidence: Stated in the write-up.

There is no information provided about pricing, monetization strategy, or business model.

Finding: Not evidenced.

The author states:

• Built with Codex and GPT 5.6.
• Uses TypeScript, Next.js, React, Zod, Playwright, Electron, Expo tools, SwiftUI verification harnesses.
• Includes unit tests (551), browser scenarios (29), and a 10,000 node benchmark.
• Has a hosted Judge Mode with no account or API key required.
• Is open-source on GitHub.

Inference: The tool is built using modern web and mobile development stacks, with strong emphasis on testing and validation.

Claim: The system uses AI for interpretation and judgment but keeps deterministic systems for repeatable actions.

Evidence: Stated in the write-up.

Claim: Codex was used throughout the lifecycle of the project — from planning to release.

Evidence: Stated in the write-up.

There is no evidence of:

• Revenue
• Customers or users
• Adoption metrics
• Product usage data
• Market traction beyond the author’s own development

Finding: Not evidenced.

The description does not mention any competitors. It references Figma and Paper as inspirations but does not compare IntentForm to existing tools in this space.

Finding: Not evidenced.

• The entire product is described as being built by one person (Francesco Giannicola).
• No evidence of real-world usage or feedback from users.
• Relies heavily on AI tools (Codex, GPT 5.6) for development — raises questions about scalability and reliability if those tools change or become unavailable.
• The author claims to have used AI extensively but does not provide any data or metrics showing how effective that was.
• No mention of security, performance, or integration capabilities beyond basic functionality.

Inference: Risk of over-reliance on a single developer and unproven market demand.

Evidence: Author states solo development; no evidence of traction or adoption.

1. What is the actual user base or pilot group for this tool?
2. How does IntentForm handle edge cases in platform-specific behavior (e.g., accessibility, safe areas)?
3. Can you demonstrate how a real team would use it in practice?
4. Are there any plans to integrate with existing design tools like Figma or Sketch?
5. What are the technical limitations of the current semantic graph approach?
6. How does IntentForm deal with version control and collaboration between developers?
7. Has the tool been tested under load or in production environments?