Bilingual

Show HN: 1,250 SwiftUI components, and an MCP that writes them into your app
2 days ago
- Provides real, compiled SwiftUI components with live iOS Simulator screenshots and exact source code.
- Components are self-contained and can be copied directly into Xcode projects without dependencies.
- Designed for AI coding tools like Claude Code and Cursor, using real UI instead of hallucinated layouts.
- Every image is a genuine simulator screenshot; the code shown is the exact source that produced it.
- Supports iOS 17 and above, using pure SwiftUI with minimal UIKit shims.
A Chain Reaction — overreacted
2 days ago
- Web standards like HTML tags allow developers to use conceptual names (e.g., `<p>`, `<i>`) without knowing the underlying browser implementation details.
- Naming concepts enables abstraction, letting developers build complex systems by layering behaviors, such as defining custom components like `Greeting`.
- Custom components (e.g., `<Greeting>`) must be translated into browser-understood tags via functions that substitute them with their definitions (e.g., an `ExpandableGreeting` function outputs `<details>` with inner JSX).
- The translation process recursively resolves nested custom components until only built-in tags remain, akin to a chain reaction dissolving user-defined concepts into browser-ready code.
- Implementing this translation involves handling both custom functions and built-in tags, ensuring children of built-in tags are also processed recursively.
- The translation can occur on either the server or client side, but must complete before the browser renders the final output.
The Two Reacts — overreacted
2 days ago
- React components can run on either the client (user's device) or the server (creator's device), each with distinct advantages.
- Client-side components enable instant interactivity (e.g., counter) by using local state and avoiding network delays, following UI = f(state).
- Server-side components can access local data sources (e.g., file system) and preprocess data before sending only the needed UI, following UI = f(data).
- The two paradigms are seemingly incompatible: client needs state and low latency, server needs data and centralized processing.
- Real applications often require both patterns, prompting the need to split components across environments while preserving React's composability.
Gsxui – Shadcn-style components for Go
5 days ago
- gsxui is a shadcn-style component set for gsx, a Go frontend framework.
- Components are copy-in, type-checked, and server-rendered, giving developers full ownership of the code.
- Style components with Tailwind CSS and ship them easily.
- Installation involves running 'go install' for gsxui, then 'gsxui init', and adding components like button with 'gsxui add button'.

components

Show HN: 1,250 SwiftUI components, and an MCP that writes them into your app

A Chain Reaction — overreacted

The Two Reacts — overreacted

Gsxui – Shadcn-style components for Go