Answers about Liquidify implementation, package availability, contribution, and support boundaries.
These answers distinguish the implementation used by this website from planned services and unverified distribution channels. Use the linked guides for the details of a specific task.
No. Liquidify exports React components. Similar concepts can help explain composition and state, but SwiftUI modifiers, lifecycle behavior, and platform services do not transfer to JSX. Read Coming from SwiftUI.
The website uses the installed Liquidify artifacts in its checkout. Use the component catalog for APIs and examples and Codex guidance for design decisions and known composition limits. A matching version label alone does not prove that another checkout or package contains the same implementation.
As checked on October 21, 2026, the public npm latest metadata for @liquidify/react identifies 0.0.0-placeholder, described as a reserved package. It is not the usable implementation demonstrated here. Follow package availability and the local integration guidance for an authorized checkout; do not assume a public release is ready.
No account or persistence service is supplied by the controls documented here. Application code owns requests, storage, authentication, and confirmed outcomes. Liquidify Form groups content visually; a native <form> supplies browser submission semantics. See Forms and Login.
No. Theme and contrast settings affect participating styles and surfaces, but the application must review labels, focus, keyboard behavior, contrast, and content over actual backgrounds. Read Color and Accessibility. Browser rendering and application composition also need review.
Contact us lists the evidence needed for a useful report and the current gap in verified public channels. If you have authorized source access, use the contribution overview. No response timetable, release commitment, or paid support service is established here.
Read the LICENSE included with the exact source or package you use. The checked project files identify Apache License 2.0 with the Commons Clause condition; describing them as unqualified Apache 2.0 would omit part of the terms. Originality and attribution identifies the project evidence and separates it from third-party sources. Commercial arrangements beyond the published terms remain unverified.
Spanish and French versions of these English-first articles are explicitly marked translation pending. A slot labelled “Figure in preparation” is a planned visual, not a completed capture. Use the English article and its text explanation while those assets are pending.